I wouldn't recommend that approach. When the user hits the back button, they'll jump out of the wizard entirely rather than going back to the previous page (which is what a web user will expect). Cue the reports of "the wizard is broken!" ;)
-Brian On Wed, May 12, 2010 at 5:25 AM, Rahul Mohan <rahul.mo...@tcs.com> wrote: > Hi, > > I would recommend the first option. Session memory usage has a much bigger > impact than multiple hits to the server as the memory usage grows linearly > with the number of users. For retaining the previous view state, the best > solution I have seen is to use a single page application, where each page > in the wizard is downloaded as an HTML fragment and added to the divs > inside the main page. That way, the previous 'pages' are just hidden divs > and to go 'back' just unhide the previous div. ( Think of it as an Ajax > based tabbed pane without the tab buttons. ) > > - rahul --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
