* Concern: Multiple storages would mean scheduler's proxies need to know which storage to talk to
* Need to write tests for Mud::Obj storage, Mud::FS, Mud::Obj::Event
* Create standard exception format and use it in Freezer, etc.

-- Original note
Rewriting mpMUD:
  * Start with a standard architecture for persistent and non-persistent objects, transactions, context separate from transactions, components, serializable code objects.
  * Check at every step for memory leaks.
  * Build a library of unit tests.
  * Keep components separated so they can be tested individually
  * Document interfaces 
  * Modules become persistent objects, written in a non-binary format, that the world objects inherit.
