rpc_server_inq_bindings(3rpc)Returns binding handles for communications with a server Used by server applications. Synopsis #include <dce/rpc.h> void rpc_server_inq_bindings( rpc_binding_vector_t **binding_vector, unsigned32 *status); Parameters Input None. Output
binding_vector
status
Description · rpc_server_use_all_protseqs( ) · rpc_server_use_all_protseqs_if( ) · rpc_server_use_protseq( ) · rpc_server_use_protseq_ep( ) · rpc_server_use_protseq_if( ) The returned binding vector can contain binding handles with dynamic endpoints and binding handles with well-known endpoints, depending on which of the preceding routines the server application called. The rpc_intro(3rpc) reference page contains an explanation of dynamic and well-known endpoints. A server uses the vector of binding handles for exporting to the name service, for registering with the local endpoint map, or for conversion to string bindings. If there are no binding handles (no registered protocol sequences), this routine returns the rpc_s_no_bindings status code and returns the value NULL to the binding_vector parameter. The server is responsible for calling the rpc_binding_vector_free( ) routine to deallocate the memory used by the vector.
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_no_bindings
Related Information rpc_ep_register_no_replace(3rpc) rpc_server_use_all_protseqs(3rpc) rpc_server_use_all_protseqs_if(3rpc) rpc_server_use_protseq_ep(3rpc) rpc_server_use_protseq_if(3rpc)
|