A background sleeper (as opposed to worker) that would fire a signal upon timer expiration seems like a nice mechanism.
Cheers, Paulo Köch On Tue, Mar 17, 2009 at 01:04, Jeff FW <jeff...@gmail.com> wrote: > > When you say "audit"--what do you mean? By that, I mean, what do you > plan to do with the data? Do you need to know the second someone > times out, or can you check later? > > If you need to know immediately, I think you may need to do something > terrible with JavaScript. If not, or you can at least wait a little > while--run a cron job (every minute, if you'd like) that finds all of > the sessions that are past their expiration date. You can log them as > you'd like, and then clear them out. > > -Jeff > > On Mar 16, 8:56 pm, Huuuze <huu...@ymail.com> wrote: >> Jeff (and Jacob)... >> >> I appreciate your responses and I stand corrected. With that being >> said, are either of you (or anyone reading this) aware of a method >> that would allow me to track idle session timeouts? I'd like to audit >> when a user has been logged out due to a timeout. >> >> Huuuze >> >> On Mar 16, 7:49 pm, Jeff FW <jeff...@gmail.com> wrote: >> >> > It's not a bug. When a cookie expires, the browser stops sending it >> > with its requests--therefore, there is *no* way for Django to know >> > that the cookie (and therefore, the session) has expired. There is no >> > "timeout" happening on the server side, so the session can't get >> > cleared out. Hence, why the documented method for clearing out old >> > sessions. >> >> > Maybe you're used to something like PHP's behavior, which cleans old >> > old sessions automatically. However, it only does this by deciding to >> > clear out the old sessions (by default) 1 out of every 100 requests-- >> > which is kind of a nasty thing to do that 100th person. >> >> > -Jeff >> >> > 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 -~----------~----~----~----~------~----~------~--~---
