On Thu, Jun 18, 2009 at 10:43 AM, Gurkan Erdogdu<[email protected]> wrote: > AFAIK, Terracotta provides distributed cache for multiple nodes. And > generally it is used for saving user sessions for fail-over scenarios. Does > wicket use it for clustering page data? >
Yes, there is terracotta support for wicket page state, so that it replicates across nodes. Pretty slick from what I understand, but I haven't had a chance to use it yet. > Actually, we have not implemented the session related scenarios like > activation/passivation of the sessions. For example, when container > passivates session, passivation occurs and OWB will passivate all component > instances that have passivated capable scope types (like session and > conversation scopes). I think that this can be easily done by implementing > the HttpSessionActiovationListener. I would assume so, yes.
