G
Guest
If I am writing the server side of a client-server application using C/C++
the most scalable solution to handle requests is to use the I/O completion
port model.
In C# I discovered that asynchronous sockets use the I/O completion port
model underneath. However, I do I control how many "worker" threads are used
to service the request. I do not want the server side application spinning a
thread for every request.
Thanks,
Oldman
the most scalable solution to handle requests is to use the I/O completion
port model.
In C# I discovered that asynchronous sockets use the I/O completion port
model underneath. However, I do I control how many "worker" threads are used
to service the request. I do not want the server side application spinning a
thread for every request.
Thanks,
Oldman