The string binding is a character string that consists of several sub-strings. The strings in a string binding represent the object UUID, the protocol sequence, the network address, the endpoint, and the endpoint options.
The object UUID is a unique identifier. The protocol sequence is a string that represents the RPC network-communications protocol. The protocol sequence also determines network-address and endpoint-naming conventions. For example, the protocol sequence ncacn_ip_tcp indicates a connection-based NCA connection over TCP/IP. For more information about protocol sequences, see Specifying the Protocol Sequence or the reference entry for PROTSEQ.
The network address indicates the server name and the endpoint indicates a communication port at that server.
The client application can itself combine these substrings into the correct string-binding syntax, or it can call the function RpcStringBindingCompose. After a client calls RpcStringBindingCompose, it calls RpcBindingFromStringBinding to obtain the binding handle. For a complete description of the required syntax, see String Binding.
Most distributed applications should use the name-service functions instead of the string binding to obtain the binding handle. The name-service functions allow your server application to register its interface and object UUIDs, network address, and endpoint under a single logical name. These functions provide location independence and ease of administration.