Thanks for the replies! By large I mean lots of tabs and panels, not lots of users say 100s not 1000s. By single page app, I mean there is only one page and the user never navigates to another page. Panels come and go as required.
I do not expect to support the back button, with ajax and panel replacements. Thanks for the link on session state. Since the users will stay on a single page for a long time, and never go to a different page, do I need to be concerned with wicket not saving/serializing the page state? thanks, Bobj -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Single-page-wicket-app-tp4634756p4643219.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
