On Fri, May 17, 2002 at 11:06:42AM -0400, Greg Ward wrote:
>session information to carry around.  It seemed like a good idea to
>partition that session information into multiple objects, which made me
>think that a formal registry mapping "application names" to "application
>state" objects in every Session object was a good idea.

I was also thinking of multiple applications from different authors.
For example, someone writes a Slashdot clone using Quixote, and
someone else writes an IMAP mail browser, and you want to run both of
these on your server.  Both applications require session state, and
you can't let them step on each other's state variables.

Our site is precisely one application and so the application state
buys us nothing, but I would like to eventually see a bunch of
Quixote-based applications that can be pulled together.  (We'd likely
need to catalyze this by writing a set of small applications, and I've
wanted to do that for a while, but who know when I'll get around to
it.)

Maybe there's a better solution for this multiple-application case
than the 'application name'->'app state' idea.

--amk