I believe that we follow the servlet spec here -- concurrent requests will share the same instance of the servlet.
We may or may not support the SingleThreadModel interface, but it is deprecated in Servlet 2.5 so I would strongly suggest doing your own synchronization rather than depending on it. On Thu, Mar 31, 2011 at 11:55 AM, dilbert <[email protected]> wrote: > Thanks Don for the quick answer. I was also wandering about the GAE servlet > container implementation. If two requests arrive to the same JVM instance > will they be processed by the same servlet (object) or will the runtime > spawn two servlet objects? This is important because in the first case I > need to secure the servlet's member variables. > > Thank You 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.
