All of the atomic and locking primitives and data structures should work normally.
The thread-related classes (e.g. ExecutorService) will not work because you are still not allowed to do your own thread creation/manipulation. On Thu, Mar 31, 2011 at 6:28 AM, Thomas Visser <[email protected]>wrote: > The GAE SDK uses java.util.concurrent classes internally so I guess > they do work. However, I've never used them because when I need > locking, it should be application-wide. With java.util.concurrent you > can only achieve locking within an instance. Or am I wrong here? > > On Mar 31, 12:55 pm, dilbert <[email protected]> wrote: > > I see that the java.util.concurrent... classes are on the whitelist ( > http://code.google.com/intl/hr/appengine/docs/java/jrewhitelist.html). Are > > they implemented properly or as empty (do nothing) implementations. With > the > > new *Concurrent Requests* feature I might need some locking classes. > > > > Thanks for Your time. > > -- > 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. > > -- 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.
