OSF DCE Application Development Guide--Introduction and Style Guide

Using the DCE Name Service
Since the model described here employs object entries with only group attributes and
no binding or profile attributes, using the normal import routine should work fine.
• rpc_ns_binding_import_next( )
To read the entry’s group attribute.
The name service’s access to (and return of the binding handle from) the entry’s
group attribute is transparent and unerring because there is only one set of binding
information associated with a given entry in this scheme, and that information is
found only in the group attribute. Note that if there had been more than one member
in the group, which in fact is generally the case when group attributes are used, then
the order of return would be random. Or if there had been binding information
associated with both attributes, then here also the order in which binding handles
would be returned would be random; that is, the caller might get a handle from the
simple name attribute first, and then the handles exported to the group members, or it
might get one or more of the group’s member’s handles, then one or more of the
simple entry’s handles, and so on.
• rpc_ns_binding_import_done( )
To delete the binding import context.
The next figure illustrates this activity.
124246 Tandem Computers Incorporated 5− 29