> -- > I am also worried about texture theft, so I am thinking > that using simple encryption to encrypt the cache > and not releasing that part of the code. This would help > reduce issues like the AppThatMustNotBeNamed. > > I know that releasing the encrypt/decrypt module in binary > form would not prevent all copying, but I think that LL will > inevitably encrypt everything. > >
It would be interesting to see how client-side encryption like the cache would be successful with the open source client in 2007 that Cory mentioned yesterday at the SL town hall. > -- > I prefer multiple directory system and a "manually ran" > program that trims old data and sorts the objects in each file > You would then de-fragment the hard drive since this method will > fragment files as it goes. > > The master "UUID,resolution" to "dir,file,offset" table could > get quite large, but keeping textures that are loaded at about > the same time in the same file would speed things up. > > "Sort as you go" would work, but would be more tricky. > Databases were invented to solve all of these problems, maybe that would be a better way to go? John _______________________________________________ Libsecondlife-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/libsecondlife-dev
