[appengine-java] Re: Recommended scope for DatastoreService

2009-11-05 Thread Vince Bonfanti
Yep, I'm going though and making those changes now. Note that the Queue documentation says, "Implementations of this interface must be threadsafe." So that one's OK. Vince On Thu, Nov 5, 2009 at 12:57 PM, Roy Smith wrote: > Hi Vince > I removed all of the static qualifiers from CachingDatastore

[appengine-java] Re: Recommended scope for DatastoreService

2009-11-04 Thread Max Ross (Google)
That sounds reasonable to me. On Wed, Nov 4, 2009 at 6:50 PM, Roy Smith wrote: > Hi Max > > Thx for the answer, especially the correction on the transaction > implementation. > > The solution I'd arrived at is to use Guice to instantiate my DsS with a > scope of @RequestScoped. Do you see any pro

[appengine-java] Re: Recommended scope for DatastoreService

2009-11-04 Thread Roy Smith
Hi Max Thx for the answer, especially the correction on the transaction implementation. The solution I'd arrived at is to use Guice to instantiate my DsS with a scope of @RequestScoped. Do you see any problems with that approach? best Roy On Wed, Nov 4, 2009 at 7:02 PM, Max Ross (Google) > wr

[appengine-java] Re: Recommended scope for DatastoreService

2009-11-04 Thread Max Ross (Google)
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