[EMAIL PROTECTED] wrote:
2) However the only way I see is:
a- keep the session id in the request
b- if request.savedsessionid<>session.id then alert "session timed out"
This won't work as you expect.
Specifically, request.savedsessionid will never be there when you want
it, since a request is just that; a single http request to Zope. The
next time the user shows up, it will be a different request object...
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope maillist - [email protected]
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
