Would someone be able to explain to me the strategy that NDB uses to keep its memory, memcache and datastore entities in sync and consistent (especially during transactions)?
I can't quite figure out from the code<https://code.google.com/p/appengine-ndb-experiment/> what goes on. For example, before the start of a transaction, does NDB delete memory and memcache entities that will be affected by the transaction and then repopulate them if the transaction succeeds? I see reference to a _LOCKED<https://code.google.com/p/appengine-ndb-experiment/source/browse/ndb/context.py#27> value to lock memcache. What is this used for and what happens if the unlock operation fails? Best wishes, Dan -- 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 http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
