On Apr 21, 11:58 pm, "T.J. Crowder" <[email protected]> wrote:
> I'd also suspect you won't get a definitive answer for how things are > laid out under-the-covers from Google, because they need to keep their > implementation options open. Yes a good point and I would not expect Google to provide lots of internal details but it would be good to get confirmation that: 1. Geographically dispersed users could not complete concurrent transactions on different copies of the same entity root ID and then experience a mysterious loss of one of the transactions post commit. 2. Some idea as to whether intercontinental replication within the Datastore might lead to geographically dispersed users seeing different versions of the same committed data for a few seconds. I could cope with the latter because I would view it as a laggy version of snapshot isolation that we have experienced with conventional RDBs in recent years. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
