Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!ames!ptsfa!hoptoad!academ!uhnix1!sugar!peter
From: peter@sugar.UUCP (Peter da Silva)
Newsgroups: comp.sys.amiga
Subject: PIPE:... should it buffer at all?
Message-ID: <571@sugar.UUCP>
Date: Thu, 27-Aug-87 06:35:36 EDT
Article-I.D.: sugar.571
Posted: Thu Aug 27 06:35:36 1987
Date-Received: Sun, 30-Aug-87 08:50:48 EDT
Organization: Sugar Land UNIX - Houston, TX
Lines: 14
Keywords: PIPE: buffer UNIX pipes

It occurred to me that the most efficient way to handle PIPE: is to use the
writer's buffer to hold the data while waiting for the reader. This, of course,
would make all requests wait until the reader is ready... but Amiga PIPE:s
don't act like UNIX pipes anyway. It would allow any buffer size to be
transferred as an atomic operation.

Alternatively, how about making PIPE: act like the UNIX pipe? That is, you
can open it and write as much as you please without waiting until you fill
it up. You can have multiple writers but only one reader. The pipe hangs
around as long as a single writer *or* reader wants it. And finally you can
reopen it without losing data.
-- 
-- Peter da Silva `-_-' ...!seismo!soma!uhnix1!sugar!peter
--                  U   <--- not a copyrighted cartoon :->