大网数据广告活动
网络与域名解析

Selecting a Protocol Sequence

· 52CE 我爱测

A protocol sequence is the language that a network operating system uses to talk over the network to other computers.

A protocol sequence is the language that a network operating system uses to talk over the network to other computers. In more specific terms, RPC applications must specify a string that represents a combination of an RPC protocol, a transport protocol, and a network protocol.

Microsoft RPC supports three RPC protocols:

  • Network Computing Architecture connection-oriented protocol (NCACN)
  • Network Computing Architecture datagram protocol (NCADG)
  • Network Computing Architecture local remote procedure call (NCALRPC)

RPC applications can use the NCALRPC protocol to invoke procedures offered by server programs running on the same computer that the client program runs on. This is, by far, the most efficient method for calling functionality in a different process on the same computer.

The transport and network protocols that your application uses depend on which protocols the network supports. Many networks today, including the Internet, support TCP/IP. Other common transport and network protocols are IPX/SPX, NetBIOS, and AppleTalk DSP. Microsoft RPC supports these and other transport and network protocols. For a complete list, see Protocol Sequence Constants.

When your application uses automatic binding handles, it does not need to specify the protocol sequence. If it uses implicit or explicit handles, it must obtain or specify the protocol sequence. Each distributed system must examine the environment in which it will be deployed to determine which protocol sequence is best suited for that environment.

Not all protocol sequences have equivalent functionality. Developers should verify that the chosen protocol sequence supports the required features. In general, ncalrpc for local communications and ncacn_ip_tcp or ncacn_http for remote communications are recommended; they work in all environments, they have optimal performance, and they support all necessary, best-practice features.

Clients can also specify protocol sequence information that they obtain from Active Directory, the registry, environment variables created and initialized by the setup program, application-specific configuration files, or from literal strings in the program source code.

After your client program has a valid protocol sequence string, it can pass that information to the RpcStringBindingCompose and RpcBindingFromStringBinding functions to create the binding handle.

Source: Microsoft Learn / Windows Win32 documentation by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / Windows Win32 documentation
适用范围
Windows Win32 API · Source date 05/31/2018
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。