I agree with you, Jeff. The sessions should last (client and server side) as long as you tell them to last. On a positive note, it appears that Remi went ahead and changed the filter.
Kevin On 2/7/06, Jeff Marshall <[EMAIL PROTECTED]> wrote: > > 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 > > -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
