Quoting garbagecat10 / gmail.com, on Thu, May 11, 2006 at 01:35:58PM +0900:
> Works fine. It's not a ruby-specific issue. You have to remember to set the
> accepting socket non-blocking, and then be aware that it may return EAGAIN
> (or whatever your platform-specific equivalent is) even if it selected
> readable.
> 
> (This was two days ago and  now I can't remember the context this came up
> in. Were we talking about apps that prefer to use blocking i/o?)

I think it was in the contex of ruby's socket apis not behaving as
expected, maybe a few things got mixed up there.

Cheers,
Sam