Tuesday, October 9th, 2007
A recent post by Raymond Camden caught my attention as it focused on how to properly manage a web application’s server-side sessions when using Ajax to make server requests. In the post, the application in question uses a dashboard paradigm and has no page refreshes:
Imagine you have an Ajax-based site. The front end acts like a dashboard. In other words, the user never leaves the page, but executes various actions that do Ajaxy-type things on the back end. But if the user sits by and does nothing, how can I recognize a session timeout when the next Ajax-based call is done?
One solution thrown out was to create a ping service but as your audience grows, that’s going to send a lot of extra HTTP requests to the server. Dan Switzer offered another option as well using HTTP response headers.
So how would Ajaxian readers handle this situation?
Link to the post: How can you timeout a session in an Ajax-based application?
Posted by Rey Bango at 8:58 am