[#7872] Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...>

All, I needed a nonblocking socket connect for my asynchronous-event

18 messages 2006/05/14
[#7873] Re: Nonblocking socket-connect — Tanaka Akira <akr@...17n.org> 2006/05/14

In article <3a94cf510605140559l7baa0205le341dac4f47d424b@mail.gmail.com>,

[#7874] Re: Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...> 2006/05/15

How about introducing the method Socket#set_nonblocking, or alternatively

[#7875] Re: Nonblocking socket-connect — Yukihiro Matsumoto <matz@...> 2006/05/15

Hi,

[#7876] Re: Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...> 2006/05/15

Well, it's ok then. I'm comfortable adding in the nonblocking

[#7877] Re: Nonblocking socket-connect — Yukihiro Matsumoto <matz@...> 2006/05/15

Hi,

Nonblocking accept

From: "Francis Cianfrocca" <garbagecat10@...>
Date: 2006-05-26 12:29:33 UTC
List: ruby-core #7923
Thanks to the Matz and colleagues for adding the *_nonblock functions. They
have been a huge help. I've already gotten some big performance improvements
in the EventMachine event-processing library. I thought it was a little
strange that accept_nonblock is not available for TCPServer (because it
inherits from IO rather than Socket) but it wasn't hard to work around that.
(Just create a Socket object and call bind and listen on it myself.) The
nonblock functions seem to work well with files and unix-domain sockets. I
haven't tested datagrams yet but will do so shortly.

Thanks again, team.

In This Thread

Prev Next