[#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,

Ruby threads working with native threads

From: "Francis Cianfrocca" <garbagecat10@...>
Date: 2006-05-10 16:43:35 UTC
List: ruby-core #7858
I recently wrote a network-event extension for Ruby ("eventmachine" in
Rubyforge) and had considerable difficulty working with Ruby threads. Of
course you can guess the problem: select(2) can't be called by an extension
if more than one Ruby thread is running. I had to use a rather ugly hack to
get it to work, since there are no shared synchronization objects between
Ruby and native code.

Is it possible to call the Ruby thread scheduler directly from extension
code? Does that approach even make sense?
Does it make sense to enable Ruby's sync primitives to interoperate with
native ones?
Thank you,
-francis

In This Thread

Prev Next