ASP.NET IO thread pool and asynchronous sockets

[Navin Mishra]

Hi,

I've an ASP.NET web service that consumes other web services as well as
sends data to client using TCP blocking sockets on a custom thread pool
threads. If I use asynchronous sockets to send data to clients, would it use
threads from ASP.NET IO thread pool ? Is it a good idea ? Or could it
potentially exhaust all threads from IO thread pool and cause problems for
web service to access other web services ?

Thanks in advance and regards

Navin

 

[bruce barker]

async i/o is done on the calling thread. its basically a non-blocking
i/o. you will control which thread is used by which thread makes the
async call. for example you would not want to use the web service thread
unless your thread blocks waiting for completion (as the thread may be
destroyed before completion).

you probably want to use a pool and decide what to do when the pool is
exhausted.

-- bruce (sqlwork.com)