> I was thinking of web applications that are less "page oriented" and > more "application oriented". Where the "application" has all kinds of view > state that is Wicket's concern, such as Collapsable Menus (non-client side), > Document being viewed, and so on...
There are many ways to tackle that, and my approach for e.g. saving the state of a tree so that it gets put back in the right position again when a user revisits is to either store in a cookie or in a database. You could store it in a session as well though. > And if the user is in active long enough, > doesn't the servlet container serialize the session? That depends on the container and settings and on who manages the session in the first place. Also note that even though using HttpSession as a backing for the Wicket WebSession object is the default, it can be backed by everything you want and you can write Wicket applications without ever touching an actual HttpSession. Eelco _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
