Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site cbosgd.UUCP
Path: utzoo!linus!decvax!microsoft!uw-beaver!cornell!vax135!floyd!clyde!ihnp4!cbosgd!mark
From: mark@cbosgd.UUCP (Mark Horton)
Newsgroups: net.unix
Subject: Re: reading and writing to another process
Message-ID: <411@cbosgd.UUCP>
Date: Tue, 18-Oct-83 00:28:39 EDT
Article-I.D.: cbosgd.411
Posted: Tue Oct 18 00:28:39 1983
Date-Received: Thu, 6-Oct-83 21:57:58 EDT
References: <429@nsc.uucp>, <2399@utcsrgv.UUCP>
Organization: AT&T Bell Laboratories, Columbus
Lines: 17

It's worth pointing that the pipeline method posted by Dave
Sherman, while the ONLY portable way to do it, only works if
the two processes in question have a common ancestor and knew
they wanted a pipeline before they separated into two processes.
So it works fine for the shell, or for applications that want to
start out as a single command and break into processes.  But it
does not work for arbitrary processes to talk to each other, as
with a user/server model.

There are many methods to implement arbitrary IPC.  None of them
will work in every version of UNIX.  In fact, very few of them
will work in more than one version of UNIX.  These include (but
are not limited to)
	Named pipes		System III and V
	Messages		System V
	Sockets			4.2BSD
	Semaphores		various, all incompatible.