Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!usc!ucsd!ames!uhccux!virtue!coms2146
From: coms2146@waikato.ac.nz
Newsgroups: comp.os.misc
Subject: "Registry" info wanted
Message-ID: <725.2676656c@waikato.ac.nz>
Date: 13 Jun 90 04:10:20 GMT
Organization: University of Waikato, Hamilton, New Zealand
Lines: 22

In a local class in operating systems, we are talking about what we call
a registry. This "registers" the various facilitys/services made available
by the OS, and possibly those of user programs as well. Any programs
which wants to use these facilitys has its calls replaced by the
linker/loader by registry calls. The registry determines if the program
can access these services or not, and if so lets them be used.

What I want to know is if anyone has seen/used any facility that acts
like this, or know of any references in the literature? I have heard that
there is a networking daemon on apollo systems that acts in a similar
matter, but that may be wrong.

Please respond directly, I'll summarise here if there is enough interest...

Alistair Veitch                      Phone: +64 071 562889 ext. 8768
Internet: coms2146@waikato.ac.nz	    +64 071 562388 (home)
SNAIL: Computer Science Dept, University of Waikato, Hamilton, New Zealand

"There are two ways of constructing a software design: One way is to make it
so simple that there are *obviously* no deficiencies and the other way is to
make it so simple that there are no *obvious* deficiencies."
	- C.A.R. Hoare, 1980 Turing Award Lecture