Re: Winsock select timeout

From:

"Alexander Nickolov" <agnickolov@mvps.org>

Newsgroups:

microsoft.public.vc.language

Date:

Fri, 19 Oct 2007 13:51:06 -0700

Message-ID:

<uVjCsGpEIHA.748@TK2MSFTNGP04.phx.gbl>

Or one thread with IOCP... IOCP doesn't have the 64 handles
limitation either.

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

"Ben Voigt [C++ MVP]" <rbv@nospam.nospam> wrote in message
news:ufK5j1lEIHA.4712@TK2MSFTNGP04.phx.gbl...

"Alexander Grigoriev" <alegr@earthlink.net> wrote in message
news:eJexlmfEIHA.3548@TK2MSFTNGP06.phx.gbl...

You can only wait for 64 events.

Then two threads with WFMO. I don't think that limitation affects
alertable sleep with APCs though.

"Ben Voigt [C++ MVP]" <rbv@nospam.nospam> wrote in message
news:%23x$jUTZEIHA.5208@TK2MSFTNGP04.phx.gbl...

One thread per processor, 100 kernel events, overlapped I/O,
WaitForMultipleObjects (with bWaitAll = FALSE). Or use ReadFileEx and
completion routines with an alertable sleep (e.g. SleepEx with
bAlertable = TRUE).