> servlet world too), when a session starts and ends, you can associate an
> event with it.  So this allows you to use the session space as sort of a
> scratchpad for use when a user comes in.  At start time, you copy over
> user state to the session object (based on authentication information).
> user does some stuff, changing the contents of the session state.  Then
> the session expires, the session end event is called, the state is copied
> back to the user object.  This is something that core session tracking
> doesn't do because session ids don't expire.

Actually, the more I think about this, the more convinced I become that I
should offer something this tied to the expiration of the session data

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

Reply via email to