A DatastoreService instance is extremely lightweight so feel free to create them as-needed. In addition, transactions are not tied to a specific DatastoreService instance but rather to the thread that started the transaction. Finally, assume that all classes in the api are _not_ threadsafe unless explicitly documented otherwise.
Hope this helps, Max On Wed, Nov 4, 2009 at 4:35 AM, Roy <roy.sm...@cleverthinking.co.uk> wrote: > > Should I be creating a DatastoreService for each "session", or are > they inexpensive enough that I can have one for each Kind? I realise > that for transactions, the latter doesn't work. > > A related question is how threadsafe is an instance of > DatastoreService? > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
