On 6/9/05, Adam Hardy <[EMAIL PROTECTED]> wrote: > So what you are saying is that really all you need to do to implement > this feature is to keep the struts mapping the same and put no-cache > instructions in the page header. > > I can do that anyway without using DialogAction, right?
I found the page, which discusses the same approach: http://fy.chalmers.se/~appro/hcntl/ "What if ACTION handler [on the server] doesn't sent the result immediately [to a browser], but spools it on server and then convinces the browser to fetch it (preferably with GET method) at some other location? Then browser presumably wouldn't get the crazy idea about caching the form data. Moreover if all results are fetched at the very same URL, then browser should feel motivated to "accumulate" them in the same history slot." I came up with exactly the same idea before I saw this one, then I searched the internet. Which means that it is not that easy to invent something really new. > your further discussion lost me since I only have a vague concept of > what the terms web control and portlet actually mean. See "Web Controls in Struts and DialogAction" thread, where I collected some info about web controls and about controlling the history. Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
