On 6/8/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > On 6/7/06, Elver Loho <[EMAIL PROTECTED]> wrote: > > This behaviour is just way too weird. I'm currently developing with > > Django for work and with CherryPy for a side project and CherryPy > > doesn't store sessions beyond the lifetime of the server. I sort of > > didn't expect this behaviour from Django either. > > > > So, this a bug or a feature? And how can I turn it off? > > Turn it off with the SESSION_EXPIRE_AT_BROWSER_CLOSE setting.
That simply sets the cookie to expire when the browser is closed. That's not a solution since I've got Firefox open in 3-4 workspaces here, with several tabs in each instance. I'm sure as hell *not* going to close every last instance every time I change something in the code and want to start all over again... I think it's a bug that Django's session variables survive when the Django development server is closed. Yes, when I close the browser, it's nice that I can start it again and be greeted with my session. However, when I close the server, I expect the session to be lost. How can I tell Django to store the sessions in memory and drop them when the server is closed? Elver --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
