Are IIS/Tomcat Multi-threaded??

[Naresh Agarwal <na...@firstrain.com>]

Hi

I want to ask something about the servers ( IIS for MS-Soap, Tomcat for
Apache-Soap), which host the Soap services

Are these servers (IIS and Tomcat) multithreaded, i.e. for each request, a
new thread is spawned which handles that particular request.

If yes, then any thread safe service, which is deployed in "application"
scope can handle multiple requests, as each request would run on a separate
thread ( spawned by IIS/Tomcat), which wud access the same instance of Soap
server(deployed in Application scope).

Please clarify.

thanks,

Regards,
Naresh Agarwal

Re: Are IIS/Tomcat Multi-threaded??

[Scott Nichol <sn...@computer.org>]

IIS and Tomcat are multi-threaded, although rather than spawning new
threads, they mostly allocate threads from a pool.  Tomcat can actually be
used for two servers, one for HTTP and the other for the "JServ" protocol.
Tomcat can then be used as a servlet container with other HTTP servers (IIS,
Apache, iPlanet, etc.) by having extensions for those servers communicate
with it using the "JServ" protocol.  Each of Tomcat's servers has its own
thread pool.

Yes, a single instance of your service code handles multiple requests by
simply having multiple threads executing it.

Scott

----- Original Message -----
From: "Naresh Agarwal" <na...@firstrain.com>
To: <so...@xml.apache.org>
Sent: Friday, September 28, 2001 4:10 AM
Subject: Are IIS/Tomcat Multi-threaded??


> Hi
>
> I want to ask something about the servers ( IIS for MS-Soap, Tomcat for
> Apache-Soap), which host the Soap services
>
> Are these servers (IIS and Tomcat) multithreaded, i.e. for each request, a
> new thread is spawned which handles that particular request.
>
> If yes, then any thread safe service, which is deployed in "application"
> scope can handle multiple requests, as each request would run on a
separate
> thread ( spawned by IIS/Tomcat), which wud access the same instance of
Soap
> server(deployed in Application scope).
>
> Please clarify.
>
> thanks,
>
> Regards,
> Naresh Agarwal
>
>
>