Roadmap

Try to uncomplicate the internals a bit for the common (one-server) case to make this approach the speed of the Robot Co-op fork, while maintaining the correctness they have dispensed with. Things to try/consider:

• Make some benchmarks that simulate real-world usage. I neglected to do this when I first started, and it was only because of Ron's help that it's suitable for storing large values now. I don't want to undo all of his hard work.
• Use simpler IO routines instead of IO-Reactor. IO-Reactor is overkill for 99% of the use cases, I suspect, and I included it mostly because I'd just written it and was eager to put it through its paces.
• Consider making un-compressed/un-escaped the default
• Investigate the cost of doing thread safety. The documentation for Rob's fork implies that he removed the mutex stuff for speed. I know it has *some* cost to make it thread-safe, I just don't know how much. If it's a pretty big hit, then make an option to turn off thread safety, while keeping it thread-safe by default.

Integrate new features that have been requested/submitted.