In almost every case, memcached is the wrong place to put sessions. If the session lives somewhere else and you are just using memcached as a true cache <http://en.wikipedia.org/wiki/Cache> of the session, then you're fine. If not, and something happens to memcache, suddenly no one can log in.
On Tue, Jun 30, 2009 at 3:30 PM, Joseph Engo <[email protected]> wrote: > > I think in most cases, memcache is the wrong place to put sessions. > > > On Jun 30, 2009, at 12:16 PM, Tzury Bar Yochay wrote: > > >> On Jun 30, 10:03 pm, Brian Moon <[email protected]> wrote: >> >>> what language? >>> >> python >> >>> what session manager? >>> >> do not use one but looking for a solution >> I am not even sure if memcached would be the right tool for the task. >> I actually want to make memcached redundant which according to the faq >> it is not applicable. >> So I guess I am going to set a session table in the database and >> memcache it. >> > > -- "If you see a whole thing - it seems that it's always beautiful. Planets, lives... But up close a world's all dirt and rocks. And day to day, life's a hard job, you get tired, you lose the pattern." Ursula K. Le Guin http://www.finsel.com/words,-words,-words.aspx (My blog) - http://www.finsel.com/photo-gallery.aspx (My Photogallery) - http://www.reluctantdba.com/dbas-and-programmers/blog.aspx (My Professional Blog)
