If you code your pages correctly, you can still have the form submitted to its final destination.
Let me try to describe this: 1. User logs in and session is created. 2. User types long form, needs a smoke break and takes off for a two-hour lunch. 3. The session times out. 4. The user returns and finishes typing the form and submits it. 5. The application.cfc/.cfm catches the form submission, and checks to see if the session exists. 6. The session does not exist, so the form data is "packaged" in WDDX or is stored in hidden form fields. 7. The user gets a login screen to re-authenticate. The form data is passed along as well. 8. Once authenticated, the form is then posted to the originally-requested action page. Don't ask for code because I have not done this before, but it sounds like it should work, huh? M!ke -----Original Message----- From: Bobby Hartsfield [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 1:56 PM To: CF-Talk Subject: RE: Keeping a session alive Only if the session dies before they submit it. In that case, they are sent to the login form and the forms "post" is lost. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225867 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
