Thanks for the link, somehow I'd managed to miss that page of
documentation entirely*; it's good to know, though it indicates other
problems for the OP.

I'm not clear on why eventually consistent gets aren't an option, ie.
why all gets are indicated as being strongly consistent. Is this a
direct consequence of replication algorithm used? There are various
places in the code I'm currently developing where dirty gets are
adequate and I'd be happy to see them faster.

* As an aside, I do find the documentation on the datastore feels very
scattered. I'd much prefer sections on the underlying app engine
mechanics with less language specific guidance.

Tom.

On 22 March 2011 17:59, Jay Young <[email protected]> wrote:
> According to the docs, gets, puts, deletes, and ancestor queries are all
> strongly consistent:
> http://code.google.com/appengine/docs/java/datastore/hr/
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" 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-java?hl=en.

Reply via email to