Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 beta 3/9/83; site sdcrdcf.UUCP
Path: utzoo!linus!philabs!seismo!hao!hplabs!sdcrdcf!naz
From: naz@sdcrdcf.UUCP (Norman Azadian)
Newsgroups: net.unix-wizards
Subject: Re: RE: UNIX IPC
Message-ID: <538@sdcrdcf.UUCP>
Date: Thu, 22-Sep-83 15:23:20 EDT
Article-I.D.: sdcrdcf.538
Posted: Thu Sep 22 15:23:20 1983
Date-Received: Mon, 26-Sep-83 03:59:40 EDT
References: <2337@ncsu.UUCP>
Reply-To: naz@sdcrdcf.UUCP (Norman Azadian)
Organization: System Development Corporation, Santa Monica
Lines: 19

The author of the reference article suggested building a low-performance
IPC using unix signal/kill routines.  I thought the same thing many months
ago and decided to build it for a project.

My design had a "message switch" process which started up all the application
processes with two pipes to each.  There was a library of IPC routines that
the application processes could use to make sending and receiving messages
easy and straightforward.  In one mode of operation, the "message switch"
process spent all it's time looking for messages on it's input pipes
(this is a star system) and routing them to the appropriate output pipes.
The application processes had to poll their receive pipe similarly.
More sophisticated versions involved signals to and from the "message switch".

The signalling scheme worked well at low speeds, but started to fall apart
as the message traffic increased.  Signals seemed to just get lost in space.
This was with a vax-11/780 running 4.1bsd.  I still have the code if anybody
is interested.  I believe the strictly-polling mode works.

					NHA