If it runs every 5 minutes that could actually explain the erratic behavior. JS heartbeat is pretty much where I'm at right now.
No it doesn't have to be instant (Though it would be nice), it's mainly to clean up chat users who closed the browser or tab within a reasonable time frame. I think that's the route I'm taking, JS heartbeat every minute, and run a scheduled task once in a while to clean up. Thanks for the help guys, appreciate the brainstorming :) On Saturday, March 2, 2013 6:41:17 PM UTC-6, Peter J. Farrell wrote: > > Alan Holden said the following on 03/02/2013 06:36 PM: > > It could be event-based, not timer based. > > onSessionEnd() doesn't run when the session officially ends. It does it > periodically every 5 minutes or so and then reaps dead sessions. So if you > have an extremely low timeout (say 1-2 minutes), it may not run at all -- > especially the client reconnects in a timely fashion with the same cookies. > > My suggestion is for your client to send a JS "heartbeat" back to the > server every 1 minute with a timestamp. The results of a clients can be in > a struct -- then reap the ones with heartbeat timestamps that are too old. > You can have a scheduled task that runs once per minute to reap old clients. > > -- > Peter J. Farrell > OpenBD Steering Committee / Mach-II Lead > Developerhttp://blog.maestropublishing.com > Identi.ca / Twitter: @maestrofjp > > Please do not send me Microsoft Office/Apple iWork documents. Send > OpenDocument instead! http://fsf.org/campaigns/opendocument/ > > -- -- online documentation: http://openbd.org/manual/ http://groups.google.com/group/openbd?hl=en --- You received this message because you are subscribed to the Google Groups "Open BlueDragon" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
