> -----Ursprüngliche Nachricht-----
> Von: Matthias Bauer [mailto:[EMAIL PROTECTED]]
> Gesendet: Freitag, 27. Juli 2001 07:47
> An: [EMAIL PROTECTED]
> Betreff: Re: AW: Struts and Frames
>
>
> Andreas,
>
> in the application we are currently developing we have a
> similar problem:
>
> We have three frames from which either only the frame the
> user is currently
> clicking a button in has to be reloaded or some other frames
> need to be
> refreshed as well.
>
> What we are doing is pretty simple:
> The request action updates the user's session state and
> forwards to the frameset
> or the single frame. In case a frame is sent back, we just
> return this frame,
> otherwise we return the whole frameset. The browser then
> requests the single
> frames from the webserver which are delivered based on the
> user's session state.
>
> We do not need any JavaScript for this. The only drawback is:
> You need to
> specify in the target of the link/form if the whole frameset
> or only the single
> frame needs to be updated, because the browser does the
> refresh on the client
> side. As a consequence you can not decided whether to update
> only the single
> frame or the whole frameset based on the request parameter
> that are sent along.
>
Hmm, I see. Thanks for your answere. Have you tackeled the "back-button"
resp. "history" problem yet? If we store the request data not in the
request, but in the session the back-button becomes close to useless.
Same for bookmarking. Although the web-app could with some work provide
it's own means of history.
Andreas
