OSF DCE Application Development Guide--Core Components

RPC and Other DCE Components
Figure 14-9. Possible Information in a Server Entry
Interface UUID/version pair 1
with binding information 1
Interface UUID/version pair 1
with binding information 2
Interface UUID/version pair 1
with binding information 3
Interface UUID/version pair 2
with binding information 1
Interface UUID/version pair 2
with binding information 3
Object UUID 2
Object UUID 3
Object UUID 4
Object UUID 1
One Server Entry
Bindings
Objects
14.3.1.4 Groups
Administrators or users of RPC applications can organize searches of a namespace for
binding information by having clients use an RPC group as the starting point for NSI
search operations. A group provides NSI search operations (import_next or
lookup_next operations) with access to the server entries of different servers that offer a
common RPC interface or object. A group contains names of one or more server
entries, other groups, or both. Since a group can contain group names, groups can be
nested. Each server entry or group named in a group is a member of the group. A
group’s members must offer one or more RPC interfaces, the type of RPC object, or
both in common.
Figure 14-10 shows an example of the kinds of members a group can contain and how
those members correspond to database entries.
Figure 14-10. Possible Mappings of a Group
124245 Tandem Computers Incorporated 14− 19