My previous idea was to maintain a Timer pool based on session ids. Every time a request with a session hits your server, you reset the Timer object associated with it. If a user logs out, you cancel the respective timer. If a timer triggers, it's a timeout.
But, we can try a simpler approach. Assuming you don't need realtime audit logs, can you exploit the expired sessions not being automatically cleaned up? Cheers, Paulo Köch On Tue, Mar 17, 2009 at 20:28, Huuuze <huu...@ymail.com> wrote: > > Paulo, thank you for the link, but I don't see how that will help. To > help articulate the problem, here is a post I included on > StackOverflow.com: > >>> I would like to audit when a user has experienced an idle timeout in my >>> Django application. In other words, if the user's session cookie's >>> expiration date exceeds the SESSION_COOKIE_AGE found in settings.py, the >>> user is redirected to the login page. When that occurs, an audit should >>> also occur. > >>> Currently, I have configured some middleware to capture these events. >>> Unfortunately, Django generates a new cookie when the user is redirected to >>> the login page, so I cannot determine if the user was taken to the login >>> page via an idle timeout or some other event. > >>> From what I can tell, I would need to work with the "django_session" table. >>> However, the records in this table cannot be associated with that user >>> because the sessionid value in the cookie is reset when the redirect occurs. > >>> I'm guessing I'm not the first to encounter this dilemma. Does anyone have >>> insight into how to resolve the problem? > > > On Mar 16, 6:38 pm, Jacob Kaplan-Moss <jacob.kaplanm...@gmail.com> > wrote: >> On Mon, Mar 16, 2009 at 4:46 PM, Huuuze <huu...@ymail.com> wrote: >> > Does anyone else agree with my viewpoints on this matter? If so, >> > please post your comments in the ticket. >> >> Actually, the right way to get your viewpoint heard is to take the >> matter to the django-developers mailing list, where topics related to >> Django's development are discussed. You'll have more luck posting >> suggestions and criticism there than here or on the ticket tracker. >> >> However, please keep in mind that we're currently running up to Django >> 1.1, so it's likely that anything that's not an outright bug might be >> left by the wayside while we close bugs for the final release. If you >> don't get an immediate response, be patient and wait until a bit after >> the release when we all have a bit more time. >> >> Jacob > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
