Re: Asynchronous socket operations and threadpool

| Also, if you have sy 600 IOCP threads processing at once, there's really
no
| way to do other async operations - you can't use the .Net thread pool, as
it
| doesn't have enough threads. You certainly don't want to spin up hundreds
of
| your own threads, so pragmatically it's normally best to do things
| synchronously within the IOCP callback.

But if your returning after beginning the new async operation, then your
releasing the thread and another IOCP thread (or same one) will handle the
new callback. So you keep going. Am I wrong? Thanks for the links.

--
William Stacey [MVP]



.