I understand that it is just a cache. Yes, the valuable data from the session is reloaded when they are 'expired'.
Perhaps I phrased it wrong. The lookup for the session data is being hashed to different values when multiple instances are being used. What I was seeing was the session was being created/deleted about every other request. I don't see how that would be expected ( or desirable ) behavior. On Dec 5, 2007 12:24 AM, Simon Wilcox <[EMAIL PROTECTED]> wrote: > J.G.Konrad wrote: > > I've been having problems with session storage using memcached with more > > than one memcached instance. The sessions are expiring before they are > > supposed to. If there is only one memcached instance everything works > > like it is supposed to. > > > > Has anyone else had this problem? > > Not directly but if the session is expired from your CACHE just pull it > from the database again. > > Remember memCACHEd is just a CACHE, it's not meant to be a database. > > You shouldn't put anything critical in the CACHE that you can't get from > a reliable persistent store somewhere else. > > See http://www.eu.socialtext.net/memcached/index.cgi?sessions > > S. > > _______________________________________________ > List: [email protected] > Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst > Searchable archive: > http://www.mail-archive.com/[EMAIL PROTECTED]/ > Dev site: http://dev.catalyst.perl.org/ >
_______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ Dev site: http://dev.catalyst.perl.org/
