Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!decvax!duke!unc!mcnc!idis!mi-cec!dvk
From: dvk@mi-cec.UUCP (Dan Klein)
Newsgroups: net.unix-wizards
Subject: Unix IPC
Message-ID: <154@mi-cec.UUCP>
Date: Mon, 19-Sep-83 11:16:59 EDT
Article-I.D.: mi-cec.154
Posted: Mon Sep 19 11:16:59 1983
Date-Received: Mon, 19-Sep-83 22:30:24 EDT
Lines: 15

Clearly, the signalling mechanism currently in Unix is far from optimal
for anything other than the most simpleminded IPC.  The mailbox approach
is reasonable, but tricky, since you need to have a way of passing the
names of the mailbox (for which you need IPC already), or just making it
an open file which gets transferred via exec.

There is one advantage to signals which cannot be overlooked in this
discussion: they have the ability to interrupt you.  Pipes do not.  Perhaps
having a VMS style AST to interrupt you on file/terminal activity is the
way to go. This way you get notice when a communicating process has something
to say, or you can simply poll things.  This makes useful programs (like
multi-player interactive games) easy to write.  They just do their real-time
things until the player changes some state by issuing a command.

(Sorry for the stream of consciousness...)