Hi!
The setup:
-Zope 2.2.4
-Core Session Tracking 0.7
-Cookie session ID manager (path=/,lifetime=0)
-Internal Session Data Manager (timeout set to 60 minutes)
This seems to randomly (but sometimes very frequently) loose session data items
:-(
FYI, you are not the only one.. I also
Christian Scholz wrote:
FYI, you are not the only one.. I also experienced that. That's also the reason
why I am back to using SQLSession again..
How hard was that to swap in?
(actually I was too lazy to track it down..)
Well, if it makes any difference, it doesn't _appear_ to happen in
Well, if it makes any difference, it doesn't _appear_ to happen in Zope
2.3.1b1,
but there are other reasons (Catalog, buggy Python Scripts) why we can't
currently move our production servers to 2.3.1b1-3...
Hmmm... this sounds like a bug in expiration code. I sent Chris a
prerelease
Hi!
FYI, you are not the only one.. I also experienced that. That's also the reason
why I am back to using SQLSession again..
How hard was that to swap in?
depends. Of course the API is not the same.. So it depends if you've factored out
the session stuff in some dtml or python method
Chris McDonough wrote:
Hmmm... this sounds like a bug in expiration code. I sent Chris a
prerelease CoreSessionTracking 0.8 which has new expiration code. Hopefully
I can release soon. I know I've been saying that for a while now... ;-)
I'm checking this out right now :-)
Christian,
