Hi Uwe,

There are no pagemaps since 1.5.0.
Only the last used stateful page instance is kept in the memory (as an
attribute in the http session).
The Memcached Session Manager for Tomcat is just an internal of how Tomcat
will manage its http sessions.
For the application there is no change at all. Wicket still will use the
Servlet APIs and Tomcat will do something different than what it does by
default without exposing this to you.

On the other hand if you provide your own implementation of Wicket's
ISessionStore (I know the code in 1.5/6.x better than 1.4.x but I guess it
is similar in 1.4.x too) then you can store Wicket's Session and the last
stateful page instance in something else than the Http Session, e.g. in

In all cases your app should be able to work without sticky sessions
because if a Tomcat node goes down for any reason then your clients will be
directed to other node(s).

On Sun, Jun 30, 2013 at 2:09 PM, uwe schaefer <u...@codesmell.de> wrote:

> On 06/29/2013 03:49 PM, William Speirs wrote:
>> Another consideration is if you're using any authentication
>> Been there, still have the bite marks from that :-)
> *g* thanks Bill, i planned to do session clustering, but have the pagemap
> seperate, so that i hopefully would not run into this.
> cu uwe
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: 
> users-unsubscribe@wicket.**apache.org<users-unsubscr...@wicket.apache.org>
> For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to