OSF DCE Application Development Guide--Core Components

OSF DCE Application Development Guide—Core Components
• A server binding handle that refers to compatible binding information that contains
the following:
— A protocol sequence from the client’s server binding information
— The same RPC protocol major version number that the client runtime supports
— At least one transfer syntax that matches one used by the client’s system
To identify the endpoint of a compatible server, the endpoint service uses the following
rules:
1. If the client requests a nonnil object UUID, the endpoint map service begins by
looking for a map element that contains both the requested interface UUID and
object UUID.
a. On finding an element containing both of the UUIDs, the endpoint map
service selects the endpoint from that element for the server binding
information used by the client.
b. If no element contains both UUIDs, the endpoint map service discards the
object UUID and starts over (see rule 2).
2. If the client requests the nil object UUID (or if the requested nonnil object UUID
is not registered), the endpoint map service looks for an element containing the
requested interface UUID and the nil object UUID.
a. On finding that element, the endpoint map service selects the endpoint from
the element for the client’s server binding information.
b. If no such element exists, the lookup fails.
The RPC protocol service inserts the endpoint of the compatible server into the client’s
server binding information.
Figure 16-5 illustrates the decisions the endpoint map service makes when looking up an
endpoint for a client.
Figure 16-5. Decisions for Looking Up an Endpoint
16 − 38 Tandem Computers Incorporated 124245