struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Mitchell" <>
Subject RE: Client-side Caching???
Date Mon, 11 Nov 2002 12:19:41 GMT
Hi Jon,

This really belongs on the struts-users mailing list.  If you are not
already subscribed, you should do so.  I'm sending a copy there for further

James Mitchell
Software Engineer/Struts Evangelist

"If you were plowing a field, which would you rather use? Two strong oxen or
1024 chickens?"
- Seymour Cray (1925-1996), father of supercomputing

> -----Original Message-----
> From: Jon Ferguson []
> 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:
For additional commands, e-mail: <>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message