As developers do we have access to these session variables? If so why not just update them manually every so often during page processing? You could also override the system timeout with a cfsetting tag for these specific pages since you know they may run long.
Shawn McKee -----Original Message----- From: Ashwin Mathew [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 26, 2006 12:52 AM To: CF-Talk Subject: RE: What determines session inactivity timeouts? The session's last accessed time is updated every time a page is hit, and every time a session variable is read, written or removed. CF does not attempt to keep the session active during page processing. If you do have pages running longer than your session timeout, you'll either have to increase the session timeout, or take a long hard look at those data loading screens (?) and see if some of that can be pre-loaded and/or cached. Not that I have much JS experience, but here's a random thought - what if you ran the JS in a hidden frame? The page could execute for as long as it wanted to in the main (visible) frame, while your JS checker script could continue to run in the hidden frame, and would still allow a user to respond to session timeout warnings. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:238771 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
