Rasputin wrote:
>
> I *think* that by implementing a single threaded model, you're effectively
> declaring run to be synchronised, which means that any clients trying to
> use the servlet will block until the last client exits.
>
That's one possibility (and the way Tomcat 4 did things up
until recently). But generally you can expect the servlet
container to implement SingleThreadModel using a pool. Ref
version 2.3 of the servlet spec[1]
SRV.2.2 Number of Instances
... for a servlet implementing the SingleThreadModel
interface, the servlet container may instantiate multiple
instances to handle a heavy request load and serialize
requests to a particular instance.
SRV.2.3.3.1 Multithreading Issues
... the SingleThreadModel interface ... A servlet
container may satisfy this requirement by serializing
requests on a servlet, or by maintaining a pool of servlet
instances.
[1] http://java.sun.com/products/servlet/download.html
--
Christopher St. John [EMAIL PROTECTED]
DistribuTopia http://www.distributopia.com
___________________________________________________________________________
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
