There indeed is a minor off-by-one error: it manifests itself as
sessions timing out at most 20 seconds early.
But there is also a deeper issue which involves the fact that a session
data object is not properly removed from an older bucket when it "moves"
due to being accessed in a later timeslice; the symptom only appears
when a browser id is "reused" to start a session after it was used to
start an older one that had timed out normally. I've got almost no clue
why this happens at this point, but I'm working on it. Ugh. This is
almost certainly what Steve is experiencing.
On Mon, 2004-05-17 at 20:26, Chris McDonough wrote:
> On Mon, 2004-05-17 at 17:52, Michael Dunstan wrote:
> > Looks like session data can expire prematurely. See attached files for
> > small changes to the test rig that reports cases where
> > context.session_data_manager.hasSessionData() is False.
> > Michael
> I think you're right, good eye! The symptoms aren't consistent with
> what Steve is reporting, however (where the problem appears when using
> TemporaryStorage but not FileStorage), so I this may be a distinct
> issue. I am looking in to it now. It feels like an off-by-one error.
> - C
> Zope-Dev maillist - [EMAIL PROTECTED]
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://mail.zope.org/mailman/listinfo/zope )
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -