Something that addresses the issue -- but not the specific problem -- is to
have a save routine on your editor page that doesn't take the user
anywhere -- i.e. it calls itself, saves and deposits the user at the same
point they were in previously. That way the user can click 'save' during,
and as an integral part of, the creation process similar to best user
practice in an ordinary word processor. Keeps their work safe and, as a
byproduct, keeps the session alive.
This pre-supposes your content app doesn't automatically display a page to
the public once its save.
Cheers,
--Matt--
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Wednesday, August 08, 2001 10:10 AM
Subject: Session timeouts
What's the best way to deal with session timeouts when using
session vars to grant access to administrative areas of a site on a
server where you don't have control of the timeout settings?
I'm thinking we probably need to switch to another method of
tracking the session... I'm reluctant to move to client vars in the db,
but is that what will be necessary? What happens now is an
administrator may be, say, creating a newsletter and by the time
he composes it and saves it, the session has timed out and he's
kicked back to the login screen...
Ideas welcomed...
Gene Kraybill
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
