Hi, I just committed a demo implementation of a basic support for back and forward buttons for Ajax requests.
The code could be found at: impl: https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-jquery/src/main/java/org/wicketstuff/jquery/ajaxbackbutton examples: code: https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-jquery-examples/src/main/java/org/wicketstuff/jquery/ajaxbackbutton jetty: http://localhost:8080/backbutton/Page4AjaxBackButton/ The idea is the same as GWT: http://code.google.com/docreader/#p=google-web-toolkit-doc-1-5&s=google-web-toolkit-doc-1-5&t=DevGuideHistory Clicking on back/forward buttons notifies you at the server side and tells you the #hash which is the wicket id of the component which registered this history entry. In contrast to Wicket's back button support for non-Ajax pages (which saves the whole pages in the page store) this implementation don't creates new versions at all. It just notifies you that the buttons are clicked - you (the developer) should take care of this notification. No saving new versions leads to the known problem that you'll have no history for the page after leaving it and returning back. But it should work good enough for apps like GMail. Any feedback is welcome! Bad feedback is prefered ;-) martin-g --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]