Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ rpc_binding_from_string_binding(3rpc) — DCE 3.1

Media Vault

Software Library

Restoration Projects

Artifacts Sought

rpc_binding_from_string_binding(3rpc)  —  Subroutines

NAME

rpc_binding_from_string_binding — Returns a binding handle from a string representation;  used by client or management applications

Synopsis

void rpc_binding_from_string_binding(
unsigned_char_t ∗string_binding,
rpc_binding_handle_t ∗binding,
unsigned32 ∗status);

Parameters

Input

string_binding
Specifies a string representation of a binding handle.

Output

bindingReturns the server binding handle. 

statusReturns the status code from this routine.  This status code indicates whether the routine completed successfully or, if not, why not. 

Description

The rpc_binding_from_string_binding() routine creates a server binding handle from a string representation of a binding handle. 

The string_binding parameter does not need to contain an object UUID. In this case, the returned binding contains a nil UUID. 

If the provided string_binding parameter does not contain an endpoint field, the returned binding parameter is a partially bound server binding handle. 

If the provided string_binding parameter does contain an endpoint field, the returned binding parameter is a fully bound server binding handle with a well-known endpoint. 

If the provided string_binding parameter does not contain a host address field, the returned binding parameter refers to the local host. 

To create a string binding, call the rpc_string_binding_compose() routine or call the rpc_binding_to_string_binding() routine or provide a character string constant. 

When an application finishes using the binding parameter, the application calls the rpc_binding_free() routine to release the memory used by the binding handle. 

The rpc_intro(3rpc) reference page contains an explanation of partially and fully bound binding handles. 

Return Values

No value is returned. 

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
Success.

rpc_s_invalid_arg
Invalid argument.

rpc_s_invalid_endpoint_format
Invalid endpoint format.

rpc_s_invalid_rpc_protseq
Invalid protocol sequence.

rpc_s_invalid_string_binding
Invalid string binding.

rpc_s_protseq_not_supported
Protocol sequence not supported on this host.

uuid_s_bad_version
Bad UUID version.

uuid_s_invalid_string_uuid
Invalid format for a string UUID.

Related Information

Functions: rpc_binding_copy(3rpc), rpc_binding_free(3rpc), rpc_binding_to_string_binding(3rpc), rpc_string_binding_compose(3rpc). 

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026