Why even bother with the servlet session? That's not scalable under distributed systems. Instead store session info in DB (you can also validate/cross-refer the user's IP address, cookies, etc. for extra security) and provide your own software-based inactivity timeout.
Greg
-----Original Message-----
From: Ronald Newton [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 17, 2003 8:39 AM
To: jdjlist
Subject: [jdjlist] RE: Servlet Request Timeout Handling
Do not attempt to save it. Ask the user to restart the process.
It is possible to cater to the user a bit too much.
Might not a better case be to increase the timeout period?
Ronn
---
You are currently subscribed to jdjlist as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
You are currently subscribed to jdjlist as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
http://www.sys-con.com/fusetalk
