Re: OT - Shutting down an RS/6000 ?

Along the same lines, but a little closer to Application Space, you have
data queues, which could kinda sorta be used to emulate the same type of
function.

Where even that falls short, though, is this:

Without piping, stdout will display on the screen (or appear in an e-mail
or whatever)... piping has the resultls we're beating upon.

With data queues, you'd still need some sort of facility to dump the data
queue to the appropriate output... and every application along the stream
would have to understand what data queue it's to read from, and what one
it's to write to....

Dennis






James Rich <james@eaerich.com>@midrange.com on 11/18/2002 11:31:29 AM

Please respond to midrange-l@midrange.com

Sent by:    midrange-l-admin@midrange.com


To:    midrange-l@midrange.com
cc:
Subject:    Re: OT - Shutting down an RS/6000 ?


On Fri, 15 Nov 2002, Hans Boldt wrote:

> > However, there's still the issue of having one program call another.
One
> > standalone program cannot call another using a PLIST type of structure.
Is
> > that an issue?  Only for us old OPM dinosuars.  As the Hans's of the
world
> > drag us kicking and screaming into the newer models, we'll probably
forget
> > about the old PLIST entirely.
>
> Joe: The same issues of inter-program communication affect
> programming in most OS's, as far as I can tell. But again, OS/400
> seems to be the odd one out in that parameter passing between
> programs can indeed be bidi. The single level store probably has a
> lot to do with that, since programs running in different processes

I just had a thought on this:  can't the same thing (passing parms from
one executable to another and back again) be achieved using mmap?  I
haven't ever coded anything that used mmap and it might be a kernel
space only function.  But it does give a type of single level store for a
limited memory space (meaning that two apps access the same memory area).

James Rich