One method I use is to use the struts errors for confirmation of database updates or have pages which do so, so the user is in tune with the database activity.
-----Original Message----- From: Jon Ferguson [mailto:ferguson@;ieee.org] Sent: Monday, November 11, 2002 6:46 AM To: Struts Developers List Subject: Client-side Caching??? Greetings all, A web-application issue I'm trying to solve: Assume you have a complex web-app that requires links and input between several web-forms. The user can jump around.. and to make the application compelling.. Must be able to. Here's a scenario of interest: 1) User edits page 'A' but does not submit the form 2) User jumps to page 'B' to fill in other details or lookup something 3) User returns to page 'A' expecting to see his edits. Problem: since page 'A' was not submitted the server never saw the edits and so reconstructs the page with the old data. User sees this as a bug (developer sees this as a limitation of HTML!!!). Right now the only clean solution to this kind of problem seems to be: a) use Java with WebStart, b)use Macromedia's Flash with server-side extensions, c)Introduce some sort of client-side caching as part of Strut's Form tags or d)change the layout such that the client-naturally applies changes before proceding. Ideas? Thanks in advanced, Jon -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
