OK, thanks

Mason looks good, but seems like overkill for my modest web/html needs. (Hopefully, when/if I reach version 0.3 my ui won't look like 1997-retro. :-)

My problem is the size of the user state and the cost to instantiate it at every request. It'll be tolerable now, but if my modest application framework is used for a larger problem, it'll hit the roof.

I'll use one of the existing variants (Cache::*, BerkeleyDB, etc) for now. This potential problem can wait until later.

Again, thanks everyone, for the answers. I'll try to write my questions better next time so it won't be so confusing. :-)