I cant find the reference now, but the Datastore (and even memcache I beleive) works as a single global 'entity', there is only one.
Transactions are global too, and the datastore is consistant. basically you the application designer has to make so consideration if the app runs on a single, or 10,000 seperate servers. The interface to the datastore is consistant. On 21/04/2009, javaDinosaur <[email protected]> wrote: > > The preview release of Java for App Engine has gotten me interested in > GAE once more but an unanswered question from the early 2008 beta days > is still causing me anxiety. > > I ask this question based on my working assumption that GAE spins app > web processes at a Google data center closest to the client browser. > > If moderate App usage were to cause an App to have two active web > processes, one based in Europe and the other in West Coast America do > both sites reference one authoritative Datastore location? > > Or do Datastore API calls reference the nearest local Datastore copy? > > If the later how would concurrent updates to the same entity from > European and Californian client browsers be resolved? > > > -- Barry - www.nearby.org.uk - www.geograph.org.uk - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
