Basically you would run a _javascript_ timer in the background that would load/reset every page call. The timer would be set to expire (x) number of minutes prior to the session timeout (yours being 20 minutes). When the _javascript_ timer reaches ZERO you would notify the user that they have been idle for x amount of minutes and will timeout in (session timeout value - time elapsed).
I do have an updated set of tags for this that I have been working on that also includes an admin interface to change the values (timeout value, how many minutes before the timeout should the pop-up be presented, message to display, css support and so on) which stores the values in application variables as well as writing a txt or wddx packet so that if the server/service was restarted the setting would be retained.
If you don't find the Exchange tags to your liking and you want to take a look at what I have now, instead of rolling your own, send me an email offline at ( [EMAIL PROTECTED]), unfortunately I don't have the files here at work.
Steven Semrau
Senior Software Engineer
SRA International, Inc
-----Original Message-----
From: Doug James [mailto:[EMAIL PROTECTED]
The admin timeout is set to 20 minutes and the cfapplication timeout is set to 3 hours. I have confirmation from an MM employee that the admin timeout setting is the maximum allowed, used for security reasons, and the cfapplication can lower the time but not go over the admin time.
With all of that said, any suggestions on how to keep a session alive beyond the 20 minutes?
Doug
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
