We observed a strange (and difficult to reproduce) phenomenon when looking up an integer value in memcache from different modules (recently renamed into "services" by Google) of the same GAE app. That is, in one module, we get back the correct value in the other module, we get back 0. Obviously, a memcache lookup can always result in returning None (Python) - but a return value of 0 indicates that a value (0) is found, no?
There are a couple of patterns we use: - We use the dedicated memcache service - In module 1, we progressively increment the value using memcache.incr(...) - The lookup in module 1 is also returning the correct result - Module 2 has not updated the value before, but is merely reading it from the cache, which results in 0 We tried finding any statements from Google concerning how the memcache service behaves when it is accessed from different modules/services, but were not able to find any clues. We understand that the memcache content is not shared across different apps, but do assume that it is shared among modules/services of the same app. Has anyone experienced something similar? Thank you, Soeren -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/f374c099-5416-4920-a1ca-b81ee0d9679a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
