The BB issue wicket solves is in the context of stateful frameworks only in my opinion...I dont think the same would be an issue in stateless frameworks like struts or even with conventional jsp/servlet programming, given their stateless nature..
Excerpt from a wicket wiki page.. "Suppose you have a paging ListView with links in the ListItems, and you've clicked through to display the third page of items. On the third page, you click the link to view the details page for that item. Now, the currently available state on the server is that you were on page 3 when you clicked the link. Then you click the browser's back button twice (i.e. back to list page 3, then back to list page 2, but all in the browser). While you're on page 2, the server state is that you're on page 3. Without versioning, clicking on a ListItem link on page 2 would actually take you to the details page for an item on page 3." NOW the above problem certainly makes sense..but in the context of how wicket works..and its stateful nature.. Would be nice to have Wicket contributors feedback on this... Java Developer-3 wrote: > > Been reading about wicket and would want to know the context in which the > back button problem is being talked about..the only problem i have faced > with respect to back button is the double form submission, cant frame > myself in the right context...Can someone give a real life example of what > problem can a back button cause and how does versioning resolves it.. > > -- View this message in context: http://www.nabble.com/Back-button-support-tp16111425p16112197.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
