From: Robert Klemme <shortcutter@...>
Date: 2006-05-02T00:27:55+09:00
Subject: Re: Multiplexed I/O

2006/5/1, James Edward Gray II <james@grayproductions.net>:
> On May 1, 2006, at 1:44 AM, Minkoo Seo wrote:
>
> > I can't understand this. If ruby uses non native multithreading, then
> > all threads will run in the same process. And that implies that one
> > blocking I/O operation stop the all threads in the ruby interpreter
> > process, doesn't it?
>
> I'm pretty sure Ruby selects over sockets under the hood, to keep the
> interpreter from blocking.  I don't believe that's a perfect solution
> those as something like a large write could still block the process.

Theoretically yes, but in practice this works pretty well. Could even
be that large writes are split up by the Ruby engine.

robert

--
Have a look: http://www.flickr.com/photos/fussel-foto/