From: Seth Kurtzberg <seth@...>
Date: 2003-03-03T01:48:42+09:00
Subject: Re: Unable to do non-blocking read on socket

I guess I must be missing something, but I see nothing here that would expose 
a blocking read if in fact one were occuring.

Also, the blocking behavior only occurs when the maximum read size argument is 
supplied to the read() call.

On Sunday 02 March 2003 02:27 am, nobu.nokada@softhome.net wrote:
> Hi,
>
> At Fri, 28 Feb 2003 01:12:07 +0900,
>
> Seth Kurtzberg wrote:
> > This is with 1.8 CVS head on linux kernel 2.4.20.
>
> EAGAIN/EWOULDBLOCK should be handled in 1.8, IO#read with no
> arguments for non-blocking IO doesn't wait unreceived data.
>
> $ ruby server.rb foo &
> [1] 13697
>
> $ ruby client.rb foo
> ""
>
> $ ruby client.rb foo 3
> "hello,"
>
> $ ruby client.rb foo 5
> "hello, world"

-- 
Seth Kurtzberg
M. I. S. Corp.
480-661-1849
seth@cql.com