Don't store session state in memcached. Part of memcached is that it can crash or otherwise discard state at any time, which is irritating to your active users. Memcached is intended only for caching values that can be recovered if lost. Servlet containers have lots of options for storing state, Tapestry adds some additional.
On Mon, May 21, 2012 at 5:19 AM, captain_rhino <graeme.kitc...@axa-travel-insurance.com> wrote: > Is there any thing I have to configure or add to my tapestry project if i > want to use memcached sticky sessions please with my apache tomcat server? > Any experiances/general advice much appreciated. > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/memcached-sticky-session-tp5712867.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org