On Apr 13, 2005, at 10:24 PM, mso@oz.net wrote:
> Also, with the standard SessionManager that uses a dictionary, if I
> reload
> a static page a couple of times, it forgets I'm logged in
> (session.user is
> None).  Because my application traps this and redirects to the login
> page,
> I have to keep re-logging in.  I had to comment the redirect code to
> test
> the static pages.  I've been using DirMapping but switched to the
> standard
> SessionManager yesterday to rule out file problems.  I just switched
> back
> to DirMapping and the problem seems to be gone.  It's not losing the
> entire session, just the User object.  If I restart the server, I get
> the
> usual "session expired" message, but that's to be expected.

Because the "standard" session manager is supposed to be
persistence-choice-neutral,
it can't make itself persistent.   I imagine that you are getting
different
scgi child processes on different hits, and it is hit-or-miss as to
whether
the process serving your request happens to have the session mapping
with your
cookie.  If you are using multiple threads/processes to service
requests (as is
customary when using SCGI), and you want to use sessions,
you must provide some mechanism for sharing
the session mapping.  DirMapping is one option.  Durus with a
Persistent subclass
of SessionManager is another.  There are lots of other options, too.