> I was thinking that there may be situations where it
> would be desirable to set up a completely custom
> version of the root directory. In less extreme situations
> a user may wish to provide his own lib directory.
> In the first situation, it would be nice if one could
> set up their own custom namer, or perhaps use the
> existing namer to set up a sub-namespace to use. In
> the second situation, it would be nice if the loaders
> were able to traverse filesystems to search for the
> lib directory.
Hmmm. This could be useful from a security perspectvie
too... the objects that something could connect to would
become a function of the locally scoped environment
rather than a function of the global naming service.
Perhaps the trick is to not rely upon the file system
for resolving shared libraries, but to instead use the
namer? That way any library could be overridden in the
local namespace. That would kind of smell like COM, I
know...
Received on Wed Sep 20 09:53:31 2000
This archive was generated by hypermail 2.1.8 : Thu Sep 22 2005 - 15:12:56 PDT