Re: MsgWaitForSingleObject and named pipe. Which event am I getting ?

In comp.os.ms-windows.programmer.win32 R.Wieser <[email protected]> wrote:
>> "Overlapped I/O" on Win32 just means asynchronous non-blocking I/O.
> 
> And that, it being asynchronous, is exactly what I'm trying to evade.

Why?

It seems to me that you want async semantics in the sense that the
program should process UI messages, and process pipe input, and not
block on either.  Using a nonblocking pipe without async support 
would mean an attempt to call ReadFile would fail when no data exists.

Is the advantage of avoiding async that it avoids allocating a buffer
and providing it to the named pipe driver to populate whenever it wants?
But calling it in a polling way still requires allocating that
buffer...?