OSF DCE Application Development Guide--Introduction and Style Guide

OSF DCE Application Development Guide—Introduction and Style Guide
5.15.2 Client Import
To bind to an object managed by the server as previously described, a client performs the
following series of library calls:
rpc_ns_entry_object_inq_begin()
To set up an object inquiry context; the client application here specifies the name of
the desired namespace object entry.
rpc_ns_entry_object_inq_next( )
To return the object UUID that the server exported to the object’s entry.
This UUID (which will be passed to the rpc_ns_binding_import_begin( ) routine,
below) will enable the server host’s endpoint mapper to accurately map the incoming
remote procedure call to the server that exported this entry.
The UUID may also be used by the server itself to determine which object the client
wants to access. Note that although this set of library routines is designed to
accommodate schemes in which multiple object UUIDs have been exported to the
same entry, the model described here requires that only one object UUID (the unique
identifier of the object to bind to) be exported.
rpc_ns_entry_object_inq_done()
To delete the object inquiry context.
rpc_ns_binding_import_begin( )
To set up a binding import context.
Note that the object UUID that was returned by the call to
rpc_ns_entry_object_inq_next( ) must be passed to rpc_ns_binding_import_-
begin( ); as a result of this the import operation (rpc_ns_binding_import_next())
will return only a binding with that object UUID.
An alternative to using the binding import routines would be to use the group
member inquiry (rpc_ns_group_mbr_inq_*()) routines to learn the name of the
entry referred to in the group attribute, and then to do a direct import from that entry.
The reason for using the rpc_ns_group_mbr_inq_*() routines, rather than the
normal import functions (rpc_ns_binding_*()), would be to make sure that the group
(and not some other) attribute in the entry is read. The
rpc_ns_binding_import_next( ) routine is defined to successively exhaust the
contents of an entry’s
binding attribute
group attribute
profile attribute
5 28 Tandem Computers Incorporated 124246