MultiThreading Web Services

[=?Utf-8?B?c2FibGU=?=]

I'm a tad confused about Web Services and Multi-Threadling. I have read in
old postings that IIS handles some level of "multithreading" for a web
service. I know that technology has changed a lot since that posting and was
wondering what the current status is.

Does IIS handle some level of multi-threading for a web service? If so, is
it sufficient so that the developer need not worry with providing an extra
level of multi-threading? In the event that multi-threading is not provided
by IIS, can you point me to an article or some sort of help that tells you
how to write such a web service?

thanks for any help you can provide!

[John Saunders [MVP]]

"sable" <ab****@discussions.microsoft.comwrote in message
news:AA**********************************@microsof t.com...

I'm a tad confused about Web Services and Multi-Threadling. I have read
in
old postings that IIS handles some level of "multithreading" for a web
service. I know that technology has changed a lot since that posting and
was
wondering what the current status is.

Does IIS handle some level of multi-threading for a web service? If so,
is
it sufficient so that the developer need not worry with providing an extra
level of multi-threading? In the event that multi-threading is not
provided
by IIS, can you point me to an article or some sort of help that tells you
how to write such a web service?

IIS doesn't handle the multi-threading, ASP.NET does. Each request comes in
on a separate thread pool thread. You can also make your service itself be
asynchronous. You should consider doing this if it takes a substantial
amount of time to execute. That is because it will be tying up the thread
pool thread while it executes.
--
John Saunders [MVP]

[Spam Catcher]

=?Utf-8?B?c2FibGU=?= <ab****@discussions.microsoft.comwrote in
news:AA**********************************@microsof t.com:

Does IIS handle some level of multi-threading for a web service? If
so, is it sufficient so that the developer need not worry with
providing an extra level of multi-threading? In the event that
multi-threading is not provided by IIS, can you point me to an article
or some sort of help that tells you how to write such a web service?

Each request runs in its own thread context so generally speaking you do
not need to implement additional multi-threading.

However, if you're planning on doing a long running process, you should
perhaps split the long running process into a Windows Service and call it
from the web. That way the process can run at it's own pace without tying
up IIS.