Security

I just realized that swapping pieces of the server to a user would present a major security risk. To reduce this, there should be some redundancy(should also help with error checking). Also, locking a specific user to a specific piece (or setting the first piece he encounters as a 'favored piece) and the second... and so on... should prevent him from effectively reverse engineering everything... which will hopefully prevent hacking. Some level of security by obscurity is necessary in the case of a distributed server.

And the GPL... a horribly devisive license... why does it need to stop other licenses, even bsd. Look at it's license compatibility. By contrast the LGPL is brilliant (if only it permitted embedding) it fosters pieces of software which can later be used by anyone under any license to create software and keeps it free. The bits evolve... more are added over time... honestly... I'd prefer it if all code licensed to me was under BSD or MIT licenses... but that's not always an option. However... I would personally modify the LGPL to remove line 3 so it doesn't get GPL-ed (it fits better with my morals that way). I'd need to remove the parts about GNU. Why is this necessary... because I don't plan to work under the support model of red-hat and the other free software developers.

Write free... write BSD.

http://www-spi.lip6.fr/~queinnec/WWW/LiSP.html 94 bucks... aaahhhh. I'm just glad I don't hafta pay for software... thank goodness for free software.