On Tue, 2009-03-17 at 18:32 -0700, Huuuze wrote: [...] > As soon as the session expires, Django > updates the records in the django.sessions table. As such, the only > unique identifier for the user, "session_key", is overwritten.
This isn't what happens when a session expires at all. Django doesn't know that the session has expired because all it sees is a user arriving without a session cookie (the cookie has expired, so the browser doesn't send it). Thus, the user looks like a brand new user at that point. So far this fact (that the cookie is not sent) has been mentioned three or four times in this thread. You really have to start believing us. > If there is some straightforward way to intercept the call to update > that table at the time of the automated logout, I'm all ears. There is no automated logout, either. There is only explicit logout prior to a session being expired. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
