Re: Regarding IO Completion ports

Typically the number of handles associated with an IOCP is
significantly greater than one, thus by extension the number of
handles associated with all your IOCPs is significantly greater
than the number of IOCPs. Since an IOCP is just another
handle, chances are overwhelmingly in favor of you failing to
allocate another handle than to allocate an IOCP handle. And
considering that typically the IOCPs are created before all
the handles associated with them, I'd say the chance to fail
on allocating an IOCP handle is virtually zero.

With all that said, you don't _need_ more than a single IOCP
in your server. You'd typically end up with multiple if the server
loads external self-contained modules (DLLs) which themselves
use their own thread pools in their design. I'd consider that a
rarity. (IIS extension DLLs come to mind though.)

--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================

"SD" <sd@nospamgroup.com> wrote in message
news:D6531F65-F126-473D-8540-AD80838D1313@microsoft.com...