From: "Mauricio Fernández" <batsman.geo@...>
Date: 2003-02-27T17:37:12+09:00
Subject: Re: Unable to do non-blocking read on socket

On Thu, Feb 27, 2003 at 05:27:26PM +0900, Seth Kurtzberg wrote:
> The read call is already preceded by kernel#select(), but that doesn't help.  
> kernel#select() tells me that data is available to read, but it doesn't stop 
> IO#read() from blocking if it's buffer size is larger than the amount of data 
> available to read.

Yeah, normally I'd use IO#sys_read, but as you cannot here...

Perhaps it'd be helpful to implement IO#read in terms of IO#sys_read to
have both non-blocking buffered / non-blocking, non-buff. semantics (or
better call it IO#nb_read).
Otherwise I don't think there's much to do, as IO#read is implemented
with fread() and IO#sys_read with read()...

-- 
 _           _                             
| |__   __ _| |_ ___ _ __ ___   __ _ _ __  
| '_ \ / _` | __/ __| '_ ` _ \ / _` | '_ \ 
| |_) | (_| | |_\__ \ | | | | | (_| | | | |
|_.__/ \__,_|\__|___/_| |_| |_|\__,_|_| |_|
	Running Debian GNU/Linux Sid (unstable)
batsman dot geo at yahoo dot com

Absolutely nothing should be concluded from these figures except that
no conclusion can be drawn from them.
	-- Joseph L. Brothers, Linux/PowerPC Project)