> Well, if it makes any difference, it doesn't _appear_ to happen in Zope
> 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 CoreSessionTracking 0.8 which has new expiration code.  Hopefully
I can release soon.  I know I've been saying that for a while now... ;-)

BTW, what's the problem with the Catalog preventing you from moving to

Zope-Dev maillist  -  [EMAIL PROTECTED]
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope )

Reply via email to