Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!atexnet!cvbnet!aperez
From: aperez@cvbnet.UUCP (Arturo Perez x6739)
Newsgroups: comp.unix.wizards
Subject: Re: buffer i/o using read(2) on BSD sockets
Message-ID: <129@cvbnetPrime.COM>
Date: 19 Mar 90 19:37:02 GMT
Sender: postnews@cvbnetPrime.COM
Lines: 24

It seems that I have generated a little bit of heat (but also quite a bit of
light) with my statement that the buffering on BSD sockets is visible even
at the application's level.  I have even been accused of telling "a lie, 
excuse me, a misleading statement" in a public forum.  So now I feel I must
clarify what I meant.

You may or may not recall that I claimed that the buffering on a BSD socket
is visible to applications and sometimes even users.  For example, here's
an excerpt from a Sun 3/60 man page for tar(1):


B	Force tar to perform multiple reads (if necessary)
	so as to read exactly enough bytes to fill a block.  This
	option exists so that tar can work across the Ethernet,
	since pipes and sockets return partial blocks even
	when more data is coming.

That's my best piece of evidence.  Now, you and I may know that it's not 
strictly necessary to have this option, but there it is.

Arturo Perez
ComputerVision, a division of Prime
aperez@cvbnet.prime.com
Too much information, like a bullet through my brain -- The Police