Jason, In general you'll want to use <threadsafe>true</threadsafe>. Without threading, if additional requests come in while an instance is executing a request, the additional requests will either be handled by other instances, or placed in a pending queue to wait until an instance is free (which of these occurs depends upon app settings and characteristics). With threading enabled, an instance can handle more than one request at once.
On Mon, Dec 5, 2011 at 2:27 AM, Jason <jmitche...@gmail.com> wrote: > Hi, > > Apologies if this is clarified elsewhere but I need to make sure. I'm > basically trying to figure out if there is much benefit in using > threading inside my Java code if all of the work is done in servlets. > > Specifically, lets say I use <threadsafe>true</threadsafe> in > appengine-web.xml. Now I have a servlet mapped to, say, /testing. For > arguments sake, /testing takes 1 second to execute, and it does not > use any concurrency. > > If I receive 1 request to /testing, and then a second request 0.5 > seconds later, is the second request blocked? Or does app engine > automatically create a new thread and execute the code inside /testing > in parallel? > > Thanks > > -- > 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. > > -- 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.
