OSF DCE Application Development Guide--Core Components

RPC and Other DCE Components
a. The operation rejects the first profile element for the
interface because it refers to the wrong version numbers.
b. In the next profile element, the operation finds the correct
version numbers (2.0). The search proceeds to the associated
server entry, /.:/LandS/Cal_host_4.
2. The search ends with the indicated server entry, where the binding
information requested by the client resides:
/.:/LandS/Cal_host_4 contents:
calendar-if-uuid,2.0
binding-information
14.3.2.2.2 Example 2: Using a Default Profile for Importing an Interface
Target Interface: Statistics V1.0
1. The search for binding information associated with Statistics V1.0 starts with
the entry esther_r_profile. But the profile lacks any elements for the interface.
Thus the search reaches the default profile element, which provides the entry
name for the default profile, /.:/cell-profile:
/.:/LandS/anthro/esther_r_profile contents:
calendar-if-uuid,1.0 /.:/LandS/C_host_7 0
calendar-if-uuid,2.0 /.:/LandS/C_host_4 1
bulletin_board-if-uuid,2.0 /.:/LandS/bb_grp 2
bulletin_board-if-uuid,2.1 /.:/LandS/bb_grp 3
Zork-if-uuid,1.0 /.:/Eng/Zork_host_2 0
00000000-0000-0000-0000-000000000000,0.0 /.:/cell-profile 0
2. The search continues to the indicated default profile, /.:/cell-
profile, which contains a profile element for the requested
Statistics V1.0 interface:
/.:/LandS/cell-profile contents:
.
.
.
Statistics-if-uuid,1.0 /.:/LandS/Stats_host_6 0
.
.
.
124245 Tandem Computers Incorporated 14− 33