OSF DCE Application Development Guide--Core Components

OSF DCE Application Development Guide—Core Components
TABLE 14-1. NSI next Operations
_______________________________________________________________________
Search Operation Attributes Traversed
_______________________________________________________________________
_______________________________________________________________________
Searches for binding and object attributes of a
compatible server; reads any NSI attribute in a
search path. Returns a binding handle that
refers to a potential binding for a compatible
server, and also to a single object UUID.
rpc_ns_binding_import_next()
_______________________________________________________________________
Searches for binding and object attributes of a
compatible server; reads any NSI attribute in a
search path. Returns a list of binding handles,
each of which refers to a potential binding for a
compatible server, and also to a single object
UUID. The same object UUID is associated
with each potential binding.
rpc_ns_binding_lookup_next( )
Note that, after calling the lookup_next
operation, the client must select one binding
handle from the list. To select a binding handle
at random, the client can call the NSI binding
select routine rpc_ns_binding_select( ).For an
alternative selection algorithm, the client can
define and call its own application-specific
select algorithm.
_______________________________________________________________________
Inquire Operation Attributes Traversed
_______________________________________________________________________
_______________________________________________________________________
Reads a group attribute and returns a member
name.
rpc_ns_group_mbr_inq_next( )
_______________________________________________________________________
Reads a profile attribute and returns the fields of
a profile element.
rpc_ns_profile_elt_inq_next()
_______________________________________________________________________
14.3.1.7 Selecting the Starting Entry
When searching a namespace for an RPC interface and object, a client supplies the
name of the directory service entry where the search begins. The entry can be a server
entry, group, or profile. Generally, an NSI search starts with a group or profile. The
group or profile defines a search path that ends at a server entry containing the
requested interface identifier, object UUID, and compatible binding information.
A user may know in advance what server instance to use. In this case, starting with a
server entry for the server instance is appropriate.
14 − 26 Tandem Computers Incorporated 124245