hi

quick question about clustering: am i right to believe that putting session/pagemap data in a memcached-like storage has advantages over the tomcat session clustering in terms of latency and robust failover behaviour? i mean, the latter obviously has the data nearby (when assuming sticky sessions) whereas the first needs to grab it from (and push it to) external storage every time even though it is far more selective about what it needs.

i was wondering if tomcat session clustering can effectivly update only the dirty parts of the session data?

i'd love any kind of feedback on that topic INCLUDING 'depends'-answers :)

cu uwe

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to