Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-lcc!mordor!styx!ames!ucbcad!ucbvax!mishkin@EDDIE.MIT.EDU@apollo.UUCP
From: mishkin@EDDIE.MIT.EDU@apollo.UUCP (Nathaniel Mishkin)
Newsgroups: mod.computers.apollo
Subject: IPC
Message-ID: <8701201950.AA22033@EDDIE.MIT.EDU>
Date: Tue, 20-Jan-87 09:30:56 EST
Article-I.D.: EDDIE.8701201950.AA22033
Posted: Tue Jan 20 09:30:56 1987
Date-Received: Wed, 21-Jan-87 02:38:36 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 22
Approved: apollo@yale-comix.arpa


    I made an interprocess communications package using IPC calls. ... 
    
First, you must know that that MBX package (or the portable TCP/IP "socket"
calls) let you do all this already.

Second, assuming there's some reason that you really want to use the
IPC calls, the correct solution to your problem is to have another process
that does nothing but listen for incoming messages and queue or deliver
(using files, or shared memory, or MBX, or sockets, or whatever) INTRA-node
to the process that actually wants the data.

Note also that the IPC calls are an unreliable datagram service.  Packets
can be lost, duplicated, or received out of order.  MBX and TCP-sockets
don't have these problems.

                    -- Nat Mishkin
                       Apollo Computer Inc.
                       Chelmsford, MA
                       {wanginst,yale,mit-eddie}!apollo!mishkin

-------