The methods come from the original memcached implementation that App Engine's memcache copies. I think they wanted people to be able to port code that uses memcached without having to handle missing methods.
Judging from Brett Slatkin's Google I/O talk about PubSubHubbub it sounds like while memcache can't promise anything, values are not going to evaporate before you can do anything with them unless you are constantly writing a bonkers amount of data to memcache. -- 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.
