On 6/8/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > On Thu, 2006-06-08 at 02:21 +0300, Elver Loho wrote: > > 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.
> Move beyond the development server for a moment and think about sessions > in the more general concept. The point is, I'm doing this on the development server. It's the *development* server. It's not Apache with mod_python. And in Django's docs it is said that people should not use the development server for anything but, well, development. Everything you've just said makes a lot of sense on a production rollout. Yes, do keep sessions after shutdown. It's a great feature! But this "feature" on the development server simply makes development more difficult. So, um, could someone add a feature to the SVN version to let me turn this off? Please? Pretty please? With sugar on top? :) 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 -~----------~----~----~----~------~----~------~--~---
