Re: readv() on TCP socket returns 0

To: Mouse <mouse%Rodents-Montreal.ORG@localhost>
Subject: Re: readv() on TCP socket returns 0
From: Thor Lancelot Simon <tls%panix.com@localhost>
Date: Thu, 7 Mar 2013 16:20:49 -0500

On Thu, Mar 07, 2013 at 12:58:50PM -0500, Mouse wrote:
> 
> If you care about portability, I would recommend not counting on this.
> For example, it wouldn't surprise me if some other OSes returned zero
> for a nonblocking read with no data immediately available.  (I don't
> know of any specific examples.)

That would be a bug -- how would you detect connection close in that
case?  Clearly such a read must return EWOULDBLOCK.

Thor

Follow-Ups:
- Re: readv() on TCP socket returns 0
  - From: Mouse

References:
- readv() on TCP socket returns 0
  - From: Emmanuel Dreyfus
- Re: readv() on TCP socket returns 0
  - From: Mouse

Prev by Date: Re: readv() on TCP socket returns 0
Next by Date: Re: readv() on TCP socket returns 0
Previous by Thread: Re: readv() on TCP socket returns 0
Next by Thread: Re: readv() on TCP socket returns 0
Indexes:

Home | Main Index | Thread Index | Old Index