morgan_greywolf's Journal: Win32 SetNamedPIpeHandleState for asynchronous I/O on a pipe

Anyone know why SetNamedPipeHandleState should not be used for asynchronous I/O (i.e, 'overlapped' or 'non-blocking' I/O) on a named pipe? MSDN just says don't use it it's only here for Lan Manager 2.0 backward compatibility.

Just curious. Seems like you could use it to do non-blocking reads without setting up an OVERLAPPED structructure, etc.

hmmm

[drachenstern]

No, I don't know. I know this doesn't help, but it means people do read your blog. I'm happy to ask around for you, if that would help...