OSF DCE Application Development Guide--Core Components

OSF DCE Application Development Guide—Core Components
path can encompass every entry named as the member of a profile element that
contains the target interface identifier. A search finishes only when it finds a server
entry containing compatible binding information and the nonnil object UUID, if
requested. Search operations take the following steps when traversing a directory
service entry:
Step 1: Binding attribute
In each entry, the search operation starts by searching for a compatible
interface identifier in the binding attribute, if present.
The absence of a binding attribute or of any compatible interface identifier
causes the search operation to go directly to step 2.
The presence of any compatible interface identifier indicates that compatible
potential bindings may exist in the binding attribute. At this point, object
UUIDs may impact the search, as follows:
• If the client specified the nil object UUID, object UUIDs do not affect the
success or failure of the search. The search returns compatible binding
information for one or more potential bindings.
• If the client specified a nonnil object UUID, the search reads the object
attribute, if present, to look for the requested object UUID. This search
for an object UUID has one of the following outcomes:
— On finding the specified object UUID, the search returns the object
UUID along with compatible binding information for one or more
potential bindings.
— If a requested object UUID is absent, the search continues to step 2.
Note: If a search involves a series of import_next or lookup_next
operations, a subsequent next operation resumes the search at
the point in the search path where the preceding operation left
off.
Step 2: Group attribute
If the binding attribute does not lead to compatible binding information or if
a series of import_next or lookup_next operations exhausts the compatible
binding information, the search continues by reading the group attribute, if
present; if the directory service entry lacks a group attribute, the search goes
directly to step 3.
The search operation selects a member of the group at random, goes to the
entry of that member, and resumes the search at step 1. Unless a group
member leads the search to compatible binding information, the search looks
at all the members of the group, one by one in random order, until none
remain.
14 − 28 Tandem Computers Incorporated 124245