We have a web site that consists of several Web apps entered from a menu page. This menu page handles the credentials and passes the ID of the user to the variaous Web Apps by means of a session variable. When the session dies none of the pages will open, those that are open will not submit, and the user will be redirected to a timeout page.
The customer would like some kind of timeout notification. I've seen many tools available and tested many of them. But each of them needs to be on the active window to actually count down the session because they are using a local timer. When this is not done it results in the notification being shown on the menu window even though the session is still alive and well because of work being done in the web app's window. I thought I had found a method from http://stackoverflow.com/a/7029210/1161391
where an AJAX pagemethod was being used to do a call back to a webmethod, that polls the server to check if its session has timed out. But as it seemingly turned out, the WebMethod merely carried out a calculation of the time since the session was initially created so that call back merely established whether the originally set timeout period had passed since the session was initiated. It did not actually perform a check to see if the session had actually timed out. In addition, some of my experiments seemed to show that even though the session had austensibly died, it had in fact not died and was alive and well, making me wonder whether the call backs to webmethod on the server every thirty seconds was in fact keeping the session alive.
We really don't want to have to update all 1700 pages in the various web apps to include timeout notification controls or code. So i would be interested to know if your notification control could be posted on the menu page and then provide the notification of session timeout for each of the different web apps.