Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!ames!sdcsvax!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Re: PIPE:... should it buffer at all?  Of course it should
Message-ID: <8709082137.AA19170@cory.Berkeley.EDU>
Date: Tue, 8-Sep-87 17:37:12 EDT
Article-I.D.: cory.8709082137.AA19170
Posted: Tue Sep  8 17:37:12 1987
Date-Received: Wed, 9-Sep-87 07:30:28 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 13

>> 	So in general, if the source can jam data out faster then the 
>> destination can read it, you want buffered pipes so the destination can run
>> full speed.
>
>I quite agree. However, there's another use for pipes. While they can save a
>hell of a lot of one scarce resource (wallclock time), they do it at the
>expense of another one (memory). My suggestion was a way to use pipes
>to save a resource that is (for me, anyway) even more scarce.

	If STDIO uses 1K buffering, a 4K static PIPE: would be plenty big
enough.  4K isn't that much.

				-Matt