The way I use the session is to simply track the last visit time and optionally a user id if an account has been created. That's it. And I store the sessions in a database (so I don't waste server memory and so the session is available to multiple front-end servers).
So, if I have to abandon the the session filter because the cookie doesn't write to disk on Internet Explorer, here's what I'll be doing: - copying & pasting the sessionfilter.py - change "max-age" to "expires" so the cookie works on IE - renaming the session database table to longsession - disabling the cherrypy sessions because I have no use for them I guess that's why this is a head-scratcher: the sessionfilter does exactly what I want and I've set things up so that I don't over-extend the session data, but I can't use it because the expiration time on the session's cookie doesn't work on IE. Jeff
