OSF DCE Application Development Guide--Introduction and Style Guide

OSF DCE Application Development Guide—Introduction and Style Guide
Whenever you want to offer more than one instance of the same interface on the same
host, you must distinguish by object UUID the binding information in the name entries
exported by the servers, if it is important to distinguish among the servers when binding
to them. Otherwise, the endpoint mapper’s selection of an endpoint with which to
complete the binding from among all the servers on that host that offer the appropriate
interface will be random.
The next figure illustrates what such an object-oriented namespace should look like.
Figure 5-8. Object-Oriented Namespace Organization
Endpoint
Mapper
Server
A
Server
B
Server
C
............................................................................
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.............................................................................
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Servers’Machine
Object A.1
Object A.2
Object B.1
Object B.2
Object C.1
Object C.2
Object C.3
Object C.4
Server A
binding,
Object A.1
UUID
Server A
binding,
Object A.2
UUID
ServerB
binding,
Object B.1
UUID
ServerB
binding,
Object B.2
UUID
Server C
binding,
Object C.1
UUID
Server C
binding,
Object C.2
UUID
Server C
binding,
Object C.3
UUID
Server C
binding,
Object C.4
UUID
export
bindings
export
bindings
export
bindings
Namespace
Each entry has a name denoting the object represented, although the names are not
shown in this figure.
Under this model, clients bind to servers via named objects in the namespace, each of
which contains enough specific information in its partial binding to allow the endpoint
mapper at the destination host to choose an appropriate endpoint for the incoming RPC.
5− 18 Tandem Computers Incorporated 124246