OSF DCE Application Development Guide--Introduction and Style Guide

OSF DCE Application Development Guide—Introduction and Style Guide
• An object UUID that can optionally be used for selection among servers and/or
manager routines
• An interface UUID that identifies the interface to which the called routine belongs
• An interface version number that defines compatibility between interface versions
• An operation number that identifies a specific operation within the interface
Figure 4-1. Information Required to Complete an RPC
Protocol Sequence
Protocol Version
Transfer Syntax
Host Address
Endpoint
Object UUID
Operation Number
Interface UUID
Interface Version
Partial
Binding
Full
Binding
May Be Referred to
by Binding Handle
Binding Information
Other Information
Interface Identifier
The binding information itself covers the first five elements of the list—the protocol and
address information required for RPC communications to occur between a client and
server. (Figure 4-1 also shows the object UUID as part of the binding information. This
applies to clients, as explained in Section 4.1.2.) In RPC terminology, such a binding
can be partial or full. A partial binding is one that contains the first four elements of the
list, but lacks an endpoint. A full binding contains an endpoint as well. The distinction
is that a partial binding is sufficient to establish communications between a client and a
server host, whereas a full binding allows communications to a specific endpoint on the
server host.
In order to complete an RPC call, all of the elements listed in Figure 4-1 must be present.
The binding process consists of a series of steps taken by the client and server to create,
make available, and assemble all the necessary information, followed by the actual RPC,
which creates the final binding and routing using the elements established by the
previous steps.
4− 2 Tandem Computers Incorporated 124246