rpc_ns_entry_inq_resolution(3rpc)Resolves the cell namespace components of a name and returns partial results Synopsis #include <dce/rpc.h> void rpc_ns_entry_inq_resolution( unsigned32 entry_name_syntax, unsigned_char_t *entry_name, unsigned_char_t **resolved_name, unsigned_char_t **unresolved_name, unsigned32 *status ); Parameters Input
entry_name_syntax To use the syntax specified in the RPC_DEFAULT_ENTRY_SYNTAX environment variable, supply a value of rpc_c_ns_syntax_default.
entry_name Input/Output
resolved_name If NULL is specified on input for this parameter, nothing will be returned.
unresolved_name If NULL is specified on input for this parameter, nothing will be returned. Output
status
Description If the read was unsuccessful because the full entry was not found in the cell namespace, then the status code will be set to rpc_s_partial_results, and: · The part of the name successfully read will be returned in resolved_name · The remaining (unresolved) part of the name will be returned in unresolved_name Thus, if the status code is rpc_s_partial_results and the (non-empty) return parameter resolved_name specifies a leaf (not a directory) entry, the contents of resolved_name can be used in subsequent calls to the NSI interface to obtain a binding handle for the server that exported to the entry. This behavior allows applications to implement namespace junctions to their own internally-implemented namespaces. Using this routine, clients can attempt to bind to overqualified name entries whose resolved_name part is the name of the server entry, and whose unresolved_name part is the path name (meaningful to the server) of some object managed by the application. Calling rpc_ns_entry_inq_resolution( ) with the full name allows the client to learn what part of the name denotes the server entry it must import bindings from; it can then bind to the server, passing the rest of the name, which the server interprets as appropriate. The sec_acl_bind(~) routine, for example, works this way. The RPC runtime allocates memory for the returned resolved_name and unresolved_name parameters. The application is responsible for calling rpc_string_free( ) to free the allocated memory.
Permissions Required
Return Values Errors The following describes a partial list of errors that might be returned. Refer to the OSF DCE Problem Determination Guide for complete descriptions of all error messages.
rpc_s_ok
rpc_s_partial_results
rpc_s_invalid_name_syntax
rpc_s_unsupported_name_syntax
Related Information rpc_ns_binding_import_begin(3rpc) rpc_ns_binding_import_done(3rpc) rpc_ns_binding_import_next(3rpc) rpc_ns_binding_inq_entry_name(3rpc) rpc_ns_binding_lookup_begin(3rpc) rpc_ns_binding_lookup_done(3rpc) rpc_ns_binding_lookup_next(3rpc)
|