Xref: utzoo comp.sys.amiga:16983 comp.sys.amiga.tech:143
Path: utzoo!mnetor!uunet!husc6!mailrus!umix!rutgers!rochester!cornell!batcomputer!itsgw!imagine!pawl16.pawl.rpi.edu!jesup
From: jesup@pawl16.pawl.rpi.edu (Randell E. Jesup)
Newsgroups: comp.sys.amiga,comp.sys.amiga.tech
Subject: Re: IPC -- The Blind men... (long!)
Message-ID: <593@imagine.PAWL.RPI.EDU>
Date: 30 Mar 88 18:28:27 GMT
References: <8139@agate.BERKELEY.EDU>
Sender: news@imagine.PAWL.RPI.EDU
Reply-To: beowulf!lunge!jesup@steinmetz.UUCP
Organization: RPI Public Access Workstation Lab - Troy, NY
Lines: 40

In article <8139@agate.BERKELEY.EDU> pete@violet.berkeley.edu (Pete Goodeve) writes:
>    2.5) Common script command control of multiple processes:
>        In other words, AREXX (or future competitors).  I suppose this is
>        really a special case of (2.3), but I don't think it's synonymous
>        with it.  It gives you more freedom in melding diverse programs
>        together, but is likely (let's say certain..) to be a bottleneck
>        for other IPC applications that need speed.

>    2.6) Multiple scripts  -- "hyperamiga"?
>        An elaboration of (2.5) -- perhaps in the form of a resident
>        library -- that lets the user build up a network of interlocking
>        processes and scripts to perform the most complicated tasks he can
>        imagine. (Is that vague enough to cover everything else? (:-))

	I think there's some basic misconception here.  ARexx IS designed as
a resident library.  You can have ARexx scripts talking to other ARexx scripts,
which are talking to other applications, ad nauseum.  It shouldn't be a bottle-
neck unless the interpreted language is to slow, in shich case you can add
compiled libraries of functions to do all the dirty work.  Remember, there can
be any number of ARexx processes using the library.

>    4.4) Remote processes:
>        Networks
>        -- restricts kinds of data that can be passed (no handles, locks
>        etc.)

	With appropriately clever design, even this can be done (if there is
a way to issue a read request across the network to a handler process on
another machine.  This process would do the read, then pass the data back
across the net.  This requires preparing the filehandle for export before
passing it, and may require issuing a request for the remote node to make
a filehandle for you to associate with the local filehandle.  A bit tricky,
but certainly possible.

     //	Randell Jesup			      Lunge Software Development
    //	Dedicated Amiga Programmer            13 Frear Ave, Troy, NY 12180
 \\//	beowulf!lunge!jesup@steinmetz.UUCP    (518) 272-2942
  \/    (uunet!steinmetz!beowulf!lunge!jesup) BIX: rjesup

(-: The Few, The Proud, The Architects of the RPM40 40MIPS CMOS Micro :-)