By the way, my question below still has not been answered. Can anyone explain what would occur in the following scenario?
> My question regarding on-disk page storage relates to the use case of a > web-app deployed on a cluster. In this situation, what will happen if the > following occurs? > > 1. A user logs in to the wicket app, is directed to node1 by the load > balancer > 2. The user stays on node1 for a few requests and uses page1 a few times, > causing some older versions to be serialized to the disk on node1 > 3. The user then gets redirected to node2 by the load balancer and uses > page1 once more > 4. Now the silly user presses the back button, over and over. > > Is the page storage on node1 is replicated to other nodes? If not, what is > the behavior of Wicket running on node2? > -- View this message in context: http://www.nabble.com/Disabling-serialization-storage-of-pages-in-session--tf4768006.html#a13796998 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
