On Tue, 2009-03-17 at 23:26 +0000, Paulo Köch wrote: > 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?
Both of these solutions have the same showstopping flaw: There's no way, on the server side, to associate a timed-out user with their previous session. Because the web browser doesn't send the session cookie. This whole "request for an enhancement" is based on wanting Django to act on information it cannot possibly know about in the first place and your solution suffers from the same problem. The only way to work around something like this is to have "never expire" sessions and manually manage the timing out on the server side. 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 -~----------~----~----~----~------~----~------~--~---
