LDAP is a really great way to store library type information. It's really perfect for it. The only problem is that there aren't really any all-purpose front ends that are useful. Still, storage of library records in an LDAP directory, with a servlet front end for users, is a great solution.
You know, I was thinking, and I'm no lawyer here, but... The whole illegality happening by trading mp3's occurs by distribution, am I right? Now, when a person shares mp3's on Napster, they do not actually give them to anyone, they merely offer them for the taking. They are not forcing anyone to actually download them. In this case, wouldn't it be the people who are selecting to download the mp3's that are committing the crime? And since your download directory can be a different one than your shared directory, you can't really tell if anyone's doing anything illegal just by poking around in Napster... does this sound at all reasonably correct?
Slashdot Mirror
LDAP is a really great way to store library type information. It's really perfect for it. The only problem is that there aren't really any all-purpose front ends that are useful. Still, storage of library records in an LDAP directory, with a servlet front end for users, is a great solution.
You know, I was thinking, and I'm no lawyer here, but... The whole illegality happening by trading mp3's occurs by distribution, am I right? Now, when a person shares mp3's on Napster, they do not actually give them to anyone, they merely offer them for the taking. They are not forcing anyone to actually download them. In this case, wouldn't it be the people who are selecting to download the mp3's that are committing the crime? And since your download directory can be a different one than your shared directory, you can't really tell if anyone's doing anything illegal just by poking around in Napster... does this sound at all reasonably correct?