Three session questions:

3) Lines 33-34 of WebKit/Session.py imply that the session timeout process
is not completed. As far as I can tell, the expiring() method (which does
nothing by default) is getting called automatically at the end of a
session's timeout period, and it _appears_ in my application that the
session is indeed automatically destroyed with invalidate(). What is the
alleged truth, and can the comments be updated accordingly?

2) [0.6.1b1] It appears to me that the 'SessionStore' parameter in
Application.config is being ignored when you use webkit.cgi or wkcgi.exe
(under Windows): the app server always operates as "Dynamic" or "File" (hard
to tell the difference). If you set 'SessionStore' to "Memory", it still
saves session files to disk when you shut down the app server. It seems to
me that closing the service with "Memory" session management, should wipe
out the sessions. Has anybody else noticed this behavior? (OneShot does NOT
seem to have this problem.)

1) MY BURNING QUESTION: What is the "correct" way to
overwrite/extend/harness the expiring() method in the Session object
(Session.py)? Or is there a better approach? I just want to execute some
logging code for a specific application on session expiration. I saw some
brief recent traffic about session cleanup on 11/29-11/30 between bj and
Jeff Tavola, but it didn't completely answer the question. So far, I've only
subclassed Page. Session seems to be buried deeper in the code hierarchy,
and subclassing it seems difficult and fraught with repercussions.

Martin Doudoroff


_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to