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

Yes, I know, but what I said is the reverse.  It blocks when you _do_ supply 
the maximum read size, not when you don't.

On Sunday 02 March 2003 10:04 am, Yukihiro Matsumoto wrote:
> Hi,
>
> In message "Re: Unable to do non-blocking read on socket"
>
>     on 03/03/03, Seth Kurtzberg <seth@cql.com> writes:
> |Also, the blocking behavior only occurs when the maximum read size
> | argument is supplied to the read() call.
>
> IO#read without maximum size is supposed to read _all_ data from the
> port, so that it should naturally block.
>
> 							matz.

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