Re: mis-named setting? SESSION_EXPIRE_AT_BROWSER_CLOSE

2011-01-31 Thread Jani Tiainen
On Monday 31 January 2011 18:38:20 Tim Sawyer wrote: > > You can't stop the user from closing the browser, or switching to another > > tab, with JS. And you shouldn't try to stop them navigating away - this > > sort of thing is only likely to annoy them intensely. > > Taking this to the extreme -

Re: mis-named setting? SESSION_EXPIRE_AT_BROWSER_CLOSE

2011-01-31 Thread Tim Sawyer
> You can't stop the user from closing the browser, or switching to another > tab, with JS. And you shouldn't try to stop them navigating away - this > sort of thing is only likely to annoy them intensely. Taking this to the extreme - what do you want to happen if a person using your site has a

Re: mis-named setting? SESSION_EXPIRE_AT_BROWSER_CLOSE

2011-01-31 Thread Daniel Roseman
On Monday, January 31, 2011 3:06:29 PM UTC, Ivan Uemlianin wrote: > > Dear Tom > > Thanks for your comment. > > My use case is a "presence"-type system. When a user logs out their > status change is sent out to all other logged-in users (using comet). > If they just close the browser this

Re: mis-named setting? SESSION_EXPIRE_AT_BROWSER_CLOSE

2011-01-31 Thread Ivan Uemlianin
Dear Tom Thanks for your comment. My use case is a "presence"-type system. When a user logs out their status change is sent out to all other logged-in users (using comet). If they just close the browser this doesn't happen. I'm mulling over two possible solutions: (a) some bit of javascript

Re: mis-named setting? SESSION_EXPIRE_AT_BROWSER_CLOSE

2011-01-31 Thread Tom Evans
On Mon, Jan 31, 2011 at 2:21 PM, Ivan Uemlianin wrote: > Dear All > > Is the setting SESSION_EXPIRE_AT_BROWSER_CLOSE mis-named?  As far as I > can tell the setting doesn't influence the session expiry at all > (e.g., what happens to the django_session table on the server).  What

mis-named setting? SESSION_EXPIRE_AT_BROWSER_CLOSE

2011-01-31 Thread Ivan Uemlianin
Dear All Is the setting SESSION_EXPIRE_AT_BROWSER_CLOSE mis-named? As far as I can tell the setting doesn't influence the session expiry at all (e.g., what happens to the django_session table on the server). What this setting seems to affect is the expiry of the *cookie* in the browser. I'm