We're using servlets which also support sessions, but you have to rely on the servlet container to offer any sort of distributed session handling and this produces scalability issues past a certain point. Same thing for persistent sessions (survive restart). We also want a mechanism that can operate for multiple types of clients, not necessarily all the same type of web server.
One Session Management System to rule them all, One Session Management System to find them, One Session Management System to bring them all and in the darkness bind them. -Kal On Tue, Feb 1, 2011 at 12:42 PM, buddhasystem <potek...@bnl.gov> wrote: > > Most if not all modern web application frameworks support sessions. This > applies to Django (with which I have most experience and also run it with > X.509 security layer) but also to Ruby on Rails and Pylons. > > So, why would you re-invent the wheel? Too messy. It's all out there for you > to use. > > Regards, > Maxim > > -- > View this message in context: > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/cassandra-as-session-store-tp5981871p5981961.html > Sent from the cassandra-u...@incubator.apache.org mailing list archive at > Nabble.com. >
