On Mar 14, 2:04 am, Richard Arrano <[email protected]> wrote: > Additionally, I realize that I shouldn't be using memcache for storage > I can count on without writing to the datastore.
It depends on how crucial that storage is. I've used memcache-only sessions for my apps for two years (see http://code.google.com/p/gmemsess/), and never had a problem. In my experience it is pretty reliable - like 99.99% or so. Sessions are a nice use case because if you do lose a key, all it means is a user has to log in again. If however you are thinking of storing something that would hurt if you lost it... DON"T. I believe memcache works as limited LIFO buffer, so keys will eventually get evicted. And it can reset at any time, although this seems to only happen after maintenance. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
