> What is the recommended deployment model to support back-button usage via > undoable changes and disk-based serialized storage with Wicket? Is it only > possible using a load balancer configured to be "sticky" (keep sessions on > the same node during the lifetime of the session)?
Recommended is to use sticky sessions. But you can configure Wicket to use HttpSessionStore to work with normal cluster synchronization (the stuff that is typically shipped with app servers). You can check out http://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicket-jetty-cluster and http://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicket-jetty-cluster-pagestore for Jetty-specific work in progress where we (or rather, Matej) build an secondlevelcachesessionstore/ pagestore optimized for working in a cluster. And as a whole different approach, you can configure Terracotta to do the clustering for you. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
