> Perhaps some of the other people on the list can explain how they
> implement session management.

I wrote a module (called quixote_session_gadgets.py) which provides:
 - class SimpleSession - a session that aliases is_dirty to has_info, and
that's it.
 - SimpleSessionManager - provides a SessionManager that provides a crude
method of timing-out a session at the developer's chosen time limit.
 - a copy of class DirMapping from quixote/demo/session_demo.cgi.  I like it
because it's multi-process friendly (I use FastCGI).
 - a function (get_simple_session_manager) that ties them all together.

It's crude, and I'm not really proud of it (heck, the best part is the
DirMapping, and it's not mine!), but it makes it a two-liner to drop session
management into a driver script. It's probably not a great solution on a
production site with "lots" of users.

If anyone is interested, I'll post it.


> Hmm, I wonder if Quixote should include code for implementing
> a simple session database.

I think that would be great, but have assumed it hasn't happened yet because
of the differing pros and cons depending on how people use Quixote
(fast/s/cgi, mod_python, medusa, twisted, home-grown from python libraries,
etc...)

I gather from another recent post that ZODB is multi-process friendly.  I
assumed that it wasn't.  I'll have to revisit that.

Jason