Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!mordor!lll-tis!ptsfa!hoptoad!academ!uhnix1!sugar!peter
From: peter@sugar.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: MCC pipes
Message-ID: <149@sugar.UUCP>
Date: Wed, 10-Jun-87 00:46:59 EDT
Article-I.D.: sugar.149
Posted: Wed Jun 10 00:46:59 1987
Date-Received: Sat, 13-Jun-87 10:38:02 EDT
References: <1174@crash.CTS.COM> <279@louie.udel.EDU> <3872@jade.BERKELEY.EDU>
Organization: Sugar Land UNIX - Houston, TX
Lines: 10
Keywords: uw pipes interlace egad gaded
Summary: What do named pipes really do?

You create a named pipe with a mknod call. As a special case anyone can do
this. The pipe is therefore just another special file. You can open it
and write to it just like a file. You can open it and read from it similarly.
Unlike PIPE: pipes, a reader doesn't hang on opening... it hangs on a read.
Similarly a writer doesn't hang: it can just write its bytes and get out of
there without waiting for a reader to show up. You also don't hang on close
waiting for your coconspiritor to finish. Otherwise it's pretty much the same.

It would be nice if the MCC PIPE: would handle more packets. For example,
Examine and ExNext.