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

Asynchronous RPC over the Named-Pipe Protocol

· 52CE 我爱测

If you use named pipes (ncacn_np) as your transport protocol, you should avoid allowing a large number of idle pending calls on the server.

If you use named pipes (ncacn_np) as your transport protocol, you should avoid allowing a large number of idle pending calls on the server. With named pipes, each client waiting for a reply will have a pending named pipe read on the server, each of which requires a certain amount of kernel memory.

For example, you would not want to use a notification call for new e-mail with the named-pipe transport, because such a call would remain pending even when clients are idle, and kernel memory could be depleted. Note that this is not a problem with the other connection-oriented protocols, such as ncacn_ip_tcp.

Since named pipes are a transport protocol, your application can use them by specifying ncacn_np as the protocol in a string binding. For more information on named pipes, see Named Pipes. For details on creating string bindings, see Using String Bindings.

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)

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

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