> > From what I understand of the Servlet Spec. a servlet must be
> > contained
> > within one instance of a JVM (because of concurrency issues)
> > but, that is
> > not related to the servlet scope which pertains to the
> > semantics of your web
> > application.
> >
> > That's kinda how I've been understanding it. Please correct me if I'm
> > wrong.
>
> I just reread all the passages of the Servlet specification that use
> the word scope and cannot find a single reference to servlet scoping. The
> only scope I know of related to web applications would be data - and that is
> where the application, session, page, and request scopes are defined. The
> scoped data is maintained in other classes (for example HttpServletRequest
> for request scope and HttpSession for session scope) and have no relation to
> the servlet's internal data structures (i.e. static and class variables).
:-) I've just re-read them, as well.
It specifically states:
"For a servlet not hosted in a distributed environment, the servlet container must use
only one instance per servlet declaration. However, for a servlet implementing
SingleThreadModel interface the servlet container may instantiate multiple instances
to handle a heavy request load and serialize requests to a particular instance."
So, there it is, I guess.
Nix.
