server-side caching to avoid losing client work-in-progress 2004-08-09 - By Dean, Michael D.
Back
We have a web application where users often take an extended period of time,
due to research needs and info gathering, to populate a target document
before saving to the server side. Often, the system timeout expires or local
gremlins occur, etc.. We've discussed using notification pop-ups and a
JavaScript timer to "advise" the users to save their work but what if the
user has walked away from the desktop when the pop-up emerges? I'm
wondering if there are viable strategies for auto-magically flushing
in-process work to the server-side for caching within the ServletContext?
What would be a viable key for storing the in-process work object in the SC?
Anybody got any primers on this topic?
TIA,
Michael Dean
Sun Certified Programmer for the Java 2 Platform
Washington State Department of Corrections
ph: 360-570-6928
fx: 360-586-1333
mailto://mddean@(protected)
"Iron sharpeneth iron;
so a man sharpeneth the countenance of his friend"
- Proverbs 27:17
===========================================================================
To unsubscribe: mailto listserv@(protected) with body: "signoff JSP-INTEREST".
For digest: mailto listserv@(protected) with body: "set JSP-INTEREST DIGEST".
Some relevant archives, FAQs and Forums on JSPs can be found at:
http://java.sun.com/products/jsp
http://archives.java.sun.com/jsp-interest.html
http://forums.java.sun.com
http://www.jspinsider.com
|
|
