On Mon, 8 Nov 1999, Siros Supavita wrote:

> Hello all,
>
> >But, what is the meaning of "The servlet container can make this
> >guarantee by synchronizing access to a single instance >of the
> >servlet, or by maintaining a pool of servlet instances and
> >dispatching each new request to a free servlet."?
> >
> >Does it mean multiple instances were created (Dynamically??) under
> >server control? Any parameter to set, if any, this value, say in
> >jserv with apache
>
> I'm not really sure what does this statement mean (I'm not familiar
> with Jserv). But in servlet concept, it never creates duplicate
> instant (to handle multiple request or whatever). This is advantage
[ ... ]

This is incorrect.  The servlet engine/container *can* create multiple
instances of a servlet, and in fact this is what most do when a
servlet implements SingleThreadModel (to help alleviate the
performance penalties) -- that is what that statement means.  I
believe most servlet engines/containers also allow control of the pool
of servlet instances created (e.g. min and max).

In fact, there was nothing stopping a servlet engine/container from
creating multiple instances of a servlet even when it didn't implement
SingleThreadModel, alhtough this has been clarified in the 2.2 spec.

Milt Epstein
Research Programmer
Software/Systems Development Group
Computing and Communications Services Office (CCSO)
University of Illinois at Urbana-Champaign (UIUC)
[EMAIL PROTECTED]

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

Reply via email to