On Thu, May 17, 2012 at 6:36 PM, bobj <[email protected]> wrote: > 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?
It would be a drag for users that they would need to build up the state (i.e. navigate through all panels and such) when you restart the server (for any reason: code change, configuration change etc). So in my opinion you should care about that stuff. It is also rather difficult for people to bookmark parts of your application (although you can build your own custom in-app bookmarks/favorites for that) when you create a single page app. I am not yet a big fan of building single page apps but also don't necessarily like the 1000+ page apps either. Martijn --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
