ORG, ROI, pem - Specification 03/16/93

[Michael David WINIKOFF]

> I'm not sure I agree with that the kernel should provide the IPC. Remember
> to keep it small and clean. I would rather put the ROI into its own ROI-device.
> (oooh no, don't start to talk about devices again Andreas :-)

How do we ask the ROI device to do ROI? 
Answer: Through Inter Process Communication (IPC)

IPC simply means a facility for comminucating between processes.
Some form of it HAS to be provided in the kernel (IMHO)

> 
> One thing that I think should be possible; make an object private. You have
> to know a "password" to use it or something like that.

The object can take an extra argument (the password) and return an error
without doing anything if the password is wrong.

> 
> Maybe I have missed something fundamental (trying desperate to reach the Tao).
> Correct me if so.

A NAMESERVER (Aka Dictionary) is the solution.
One has a dictionary (either becuase the shell gave you one when you were 
created or because you asked the kernel for the default name server) which
one can ask about objects and use it to find interesting objects.

In some sense the dictionary is just like a directory (only it points to 
objects rather then files)

> 
> Arff
> 
> PS. Peter, I must say once more that the only thing that has brought MOOSE a
> similar step forward was rev. -72 :-) from Dennis, keep up your good work,
> both of you!.
> DS.
>   Arff
> sig.'s in for 1000 miles service
>         --Andreas Arff          andreasa@dhhalden.no--
> 
> 


--------------------------------------------------------------------------------
Michael Winikoff
winikoff@cs.mu.oz.au
Computer science honours. University of Melbourne, Australia.