If it is a really session data, which will be active for a short time, a few hours, and it is OK to lose them, memcached is a better solution. I were using it when I was in Yahoo.
Tong -----Original Message----- From: buddhasystem [mailto:potek...@bnl.gov] Sent: Tuesday, February 01, 2011 9:57 AM To: cassandra-u...@incubator.apache.org Subject: Re: cassandra as session store For completeness: http://stackoverflow.com/questions/3746685/running-django-site-in-multiserver-environment-how-to-handle-sessions http://docs.djangoproject.com/en/dev/topics/http/sessions/#using-cached-sessions I guess your approach does make sense, one only wishes that the servlet in question did more work for you. If I read correctly, Django can cache sessions transparently in memcached. So memcached mecomes your Session Management System. Is it better or worse than Cassandra? My feeling is that it's probably faster and easier to set up. -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/cassandra-as-session-store-tp5981871p5982024.html Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com. This message and any attachments contain information that may be RMS Inc. confidential and/or privileged. If you are not the intended recipient (or authorized to receive for the intended recipient), and have received this message in error, any use, disclosure or distribution is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to the e-mail and permanently deleting the message from your computer and/or storage system.
