memcache loosing data is to be expected. its not designed for storing original data.
session transfer suggests an issue, or maybe a id or hash collision. see also http://code.google.com/status/appengine/detail/memcache/2009/03/10#ae-trust-detail-memcache-set-error_rate On 10/03/2009, Greg <g.fawc...@gmail.com> wrote: > > Hi - > > My app uses memcache-backed sessions, and we just had a hiccup when > some users saw their session die - and more worryingly at least one > user suddenly got another user's session. > > Anyone else notice a glitch at about 14:00 EST 10th March? Or should I > be looking at my session implementation? Any feedback would be > valuable. > > Cheers! > > Greg. > > > -- Barry - www.nearby.org.uk - www.geograph.org.uk - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
