[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: LuaSocket, Win32 and select()
- From: skaller <skaller@...>
- Date: 28 Jan 2005 15:54:26 +1100
On Fri, 2005-01-28 at 15:14, Rici Lake wrote:
> If you get EWOULDBLOCK, go do something else and then wait for
> select() to return the socket as writable again. What's the problem?
It makes select() utterly useless. You might was well just
attempt to write to each socket in turn (nonblocking write I mean),
perhaps with a delay each pass all write fail and you want to
politely yield CPU to the OS.
--
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850,
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net
- References:
- LuaSocket, Win32 and select(), duck
- Re: LuaSocket, Win32 and select(), Diego Nehab
- Re: LuaSocket, Win32 and select(), Rici Lake
- Re: LuaSocket, Win32 and select(), Diego Nehab
- Re: LuaSocket, Win32 and select(), Rici Lake