On Mon, 2006-04-03 at 10:59 -0400, John (Versimedia) wrote: > > That's all intentional behavior of memcached. You are not supposed to > > care if it stores anything or not, since your application is supposed to > > be only using it to cache data that is really stored somewhere else. > > I understand that about memcached -- however if that is the case, then it > seems A:S:M is unusable. If you cannot rely on at least knowing that > memcached is not working, then you cannot store session data. Am I wrong on > this?
Well, I personally thought A::S::M was a bad idea and would never use it. It's only useful if you don't care very much whether or not your session data is reliable. However, you are not using memcached in the expected way. Expected usage is to run several memcached servers so that it can fail over to a working one if one of them goes down (losing data in the process). There is no provision in memcached for dealing with ALL of the servers going down except to continue working and telling you that it can't find any of the data you request. I think rediscovering that a server is back up might be a desirable feature to add to Cache::Memcached, but it would have to be optional. As it is, if it stops storing records on a server that is unreachable because of a network issue, and then finds the server is back and starts using it again, it could get stale data. To protect against that, you'd need to be sure that you actually stopped that server and cleared all records from it before adding it back into rotation. > Maybe the flaw is that A:S:M should work like the standard memcached > model -- it should check for session data in the memcached dbase, and if it > is not there, check the dbase for it... That would be a much more reasonable model to use. You would have to write all updates to both places. - Perrin ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Mason-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mason-users
