> I have a question regarding this... I understand that in 1.3, previous page > states are serialized to the file system and only the current page state > stays in HttpSession. How would this work in a clustered web container that > synchronizes the HttpSession object to other nodes? Do you lose the history?
You'd need to use a shared directory between nodes. I think Matej can give you a more elaborate answer soon. He's optimizing the hell out of the session stores and working for a SLCSS that works well in clusters, and the plan is to contribute that to Wicket. In the process he's also making it easier for people to implement their own SLCSS implementations (which was pretty painful because of all the magic serialization stuff that was happening there). Eelco ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
