1Pipelining streams0

["Daniel L. Weinreb" <DLW@alderaan.scrc.symbolics.com>]

Yes, the pipe implementation could be changed to grow up to a limit, but
it doesn't seem very important, and it certainly doesn't seem like a
distinction between "true" and (presumably) "false" pipes.  I certainly
do not think it should signal an error when the limit is reached; the
producer should simply wait until there's room.

How would you like if you were communicating over a network, and
suddenly your machine bombed out into the debugger because all of the
buffers were filled because you were generating data faster than the
other machine was receiving it?  Nothing has gone wrong here, so there's
no call for the debugger.

I do not understand why your example should serve to support your point.
OK, the network sometimes drops the connection; what does that have to
do with the size of the buffer?