durusmail: quixote-users: Session persistence for Quixote 2.0
Session persistence for Quixote 2.0
2005-05-26
2005-05-27
2005-05-27
2005-05-27
2005-05-27
2005-05-27
2005-05-27
2005-05-27
2005-05-28
2005-05-29
2005-05-29
2005-05-29
2005-05-28
2005-05-28
2005-05-29
2005-05-29
Sessions in mod_python (was [Quixote-users] Session persistence...
2005-05-29
Session persistence for Quixote 2.0
Titus Brown
2005-05-27
-> > I sat down and implemented simple persistent session stores for Durus,
-> > PostgreSQL, and shelve, as well as a simple directory/file based
-> > session store.  My initial distribution is available here:
-> >
-> >         http://issola.caltech.edu/~t/transfer/qx-sessions.tar.gz
->
-> I gave a quick look. A few questions/remarks.
->
-> 1. In ShelveSessionStore you are opening the database at
->     any operation, why don't open it just in the __init__?

I'm still not sure (after all the discussion on the list ;) of whether
or not that would work well with multiple processes.  It sounded like
it would under python 2.4 but not python 2.3, but I couldn't get some
of the magic for 2.3 to work under my install.

-> 2. Why .lock and .unlock are left empty? Are there reasons not to
->     specify the default locking mechanism?

Forgive me, but I wasn't smart enough to figure out how to do that
with the Python std lib.  Help?

-> 3.  Exception("unimplemented") can be replaced with the built-in
->      NotImplemented ;)

Heh.  Fine ;).

What exactly happens with multiple processes and multiple threads still
needs to be worked out in my head.  I don't have a good way to test that
at the moment; once I do (or once someone who really understands the
details comes along) I'll work on it more.

--titus
reply