Hirarchy of Naming Services

[Tristan Richardson]

>>>>>> Jan Ulbrich writes:
>
> Just use the Nameserver client "nameclt" to bind the remote server to the 
> local one: "nameclt bind MALTESREMOTENAMESERVERNAME Object 
> IOR:OBJECTSTRINGYOULIKETOLINK".
>

It is worth noting here that there is a subtle difference between using the
"bind" operation and the "bind_context" operation for federating name servers.
Using "bind" will bind another nameserver as an object (BindingType =
nobject), whereas "bind_context" will result in a binding as a context
(BindingType = ncontext).  Only in this second case may a compound name which
refers to an object in the second nameserver be resolved in a single call to
the first nameserver.

For example say nameserver 2 is bound as a context with name "/a/b" inside
nameserver 1.  An object bound as "/c/d" inside nameserver 2 can be accessed
from nameserver 1 by the name "/a/b/c/d".

If on the other hand, nameserver 2 is bound as an object, then two calls are
necessary.  A client must first resolve "/a/b" to get an object reference for
nameserver 2, and then use this to resolve "/c/d" inside nameserver 2.

Note also that "bind_context" is only available with the "-advanced" option to
nameclt.



Tristan

+--------------------------------------------------------------------+
|  Tristan Richardson                 Email:  tjr@orl.co.uk          |
|  ORL                                  Tel:  +44 1223 343000        |
|  24a Trumpington Street               Fax:  +44 1223 313542        |
|  Cambridge, CB2 1QA, UK               WWW:  http://www.orl.co.uk/  |
+--------------------------------------------------------------------+
|          ORL - The Olivetti & Oracle Research Laboratory           |
+--------------------------------------------------------------------+