On 7/25/07, Martin Minka <[EMAIL PROTECTED]> wrote:
The session handler is using power of more memcache servers to store sessions, but it does not support redundancy and in case that one of this memcache servers is lost, some sessions are lost.
i use a database (mysql) for this. memcached imho is too volatile (by design) for me. unless session data does not change too often and i can issue the reads into the cache, i wouldn't bother personally. perhaps for a site with millions of users though. not sure. you might have to look into a hybrid method of committing to both places in the off chance you restart memcached, the data is pushed out due to LRU, etc. (biggest thing is user experience and how important the data is in the session store)
