On 2017-09-02, at 13:07, Alan Altmark wrote:
> Any read() that returns a value of zero indicates eof on a file or that your
> peer has closed their end of the channel and no further data will be received.
>
> This is true of both blocking and non-blocking sockets.
>
For a non-blocking descript
, paulgboul...@aim.com wrote:
From: paulgboul...@aim.com
To: CMS-PIPELINES@VM.MARIST.EDU
Cc:
Date: Sep 2, 2017, 1:46:15 PM
Subject: Re: [CMS-PIPELINES] FILEDESCRIPTOR and binary streams?
On 2017-09-02, at 11:37, Alan Altmark wrote:
> Zero bytes IS eof on socket reads.
>
Suppo
On 2017-09-02, at 11:37, Alan Altmark wrote:
> Zero bytes IS eof on socket reads.
>
Suppose the descriptor is not a socket?
Is this true even for nonblocking reads from a socket?
-- gil
Zero bytes IS eof on socket reads.
Alan
Sent from my iPhone using IBM Verse
On Sep 2, 2017, 1:11:12 PM, paulgboul...@aim.com wrote:
From: paulgboul...@aim.com
To: CMS-PIPELINES@VM.MARIST.EDU
Cc:
Date: Sep 2, 2017, 1:11:12 PM
Subject: [CMS-PIPELINES] FILEDESCRIPTOR and binary streams
Suppose either the input or output of FILEDESCRIPTOR is expected
to be a binary stream with no particular record separators. What
does FILEDESCRIPTOR take as a "record"? The Author's Edition
doesn't make this clear. Does it insert record separators in its
output? Which? Can the programmer cont
