Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!tnc!m0154
From: m0154@tnc.UUCP (GUY GARNETT)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Hyper Functionality [was Re: An Amiga Conversion Facility (2 of 3) LONG!]
Message-ID: <803@tnc.UUCP>
Date: 25 Apr 91 13:38:38 GMT
References: <2407@swrinde.nde.swri.edu> <1991Apr18.065847.8050@agate.berkeley.edu> <MWM.91Apr18120110@raven.pa.dec.com> <1991Apr22.071413.22219@agate.berkeley.edu>
Reply-To: m0154@tnc.UUCP (GUY GARNETT)
Organization: The Next Challenge, Fairfax, Va.
Lines: 16


It seems to me that a ARexx => ppIPC program (or even function
library) could be written fairly  easily.  It would have an Arexx port
to receive commands (perhaps implement three basic commands: CreateIPC
to create a new IPC message, AddIPC(tag,data) to add an item to the
message, and SendIPC to send the thing once its built).

The reverse should also be possible: a ppIPC => Arexx program.  It
would receive IPC messages, and reformat each item into an Arexx
command, and fire it off to the current host.  a "HOST" item could be
defined, so that you could change hosts.

With these two modules, anything that understands Arexx could be
interfaced (with the appropriate Arexx script) to ppIPC.

Wildstar