[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: LuaSocket, Win32 and select()
- From: David Burgess <dburgess@...>
- Date: Fri, 28 Jan 2005 19:15:28 +1000
On Fri, 28 Jan 2005 09:39:49 +0100, Mike Pall wrote:
> As much as I hate to say a good word about M$ products: The (native)
> overlapped I/O API on Windows gets this right -- you get the event
> notification _after_ the data is received into or sent from your user-space
> buffer.
I sort of agree. With one flaw. The inversion means that with overlapped
IO and even using WSAEventSelect() one cannot test reliably if
something is writeable,
unless you initiate the opeartion and wait for it to fail (timeout).
DB
- References:
- LuaSocket, Win32 and select(), duck
- Re: LuaSocket, Win32 and select(), Rici Lake
- Re: LuaSocket, Win32 and select(), Rici Lake
- Re: LuaSocket, Win32 and select(), Diego Nehab
- Re: LuaSocket, Win32 and select(), Mike Pall