Igor Vaynberg wrote: > disadvantages being that fail over is harder unless the disk is shared > between the cluster nodes. the disk can always be replaced by a database > as well. the whole idea is relatively new and we have yet to explore its > full potential.
Yes... that is kind of gutsy. I don't know how many people are actually using replicated sessions across a cluster (my work uses cookie-stuck sessions), but it's important to have that option. (The shared resource cache is already a big hole in that support, right?) Seems like the best thing would be for the servlet container to swap Serializable session objects to disk on its own. Then we'd get the same benefit while using the session normally. Do any servlet containers do that? Nathan ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
