Yes, I'm sure that is the case not that the RIAA have Napster over a barrel. But if Napster had done it right from the start the RIAA wouldn't have had any leverage to force them to do it.
Presumably this also means that custom clients written to track who is sharing what and locate copyright violations will also be unable to connect. Just think - if Napster had forced client authentication from the start, it would have been very difficult for eg Metallica to generate a huge list of everyone sharing their songs.
Slashdot Mirror
Well, CMVC (IBM) sits on top of DB2, and I'm pretty sure Continuus uses an RDBMS at the back end.
Yes, I'm sure that is the case not that the RIAA have Napster over a barrel. But if Napster had done it right from the start the RIAA wouldn't have had any leverage to force them to do it.
Presumably this also means that custom clients written to track who is sharing what and locate copyright violations will also be unable to connect. Just think - if Napster had forced client authentication from the start, it would have been very difficult for eg Metallica to generate a huge list of everyone sharing their songs.