That's correct. The cost of creating an instance is negligible, though. It's not dissimilar to creating different MemcacheService instances with different write policies.
On Thu, Apr 1, 2010 at 4:09 PM, keyurva <[email protected]> wrote: > I use the low-level datastore API. At runtime, I want to use the new > eventual consistency on occasions and strong consistency at others. > > I was looking at the Query class to set the consistency option but > noticed that it is only available in DatastoreServiceConfig. Is it > expected that one needs to use different DatastoreService instances > for different read policies? Or am I missing something obvious? > > Thanks, > Keyur > > -- > 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]<google-appengine-java%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- Ikai Lan Developer Programs Engineer, Google App Engine http://googleappengine.blogspot.com | http://twitter.com/app_engine -- 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.
