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

Combining Pipe and Nonpipe Parameters

· 52CE 我爱测

Combining pipe and nonpipe parameters in Remote Procedure Call (RPC).

When you combine pipe types and other types in a remote procedure call, the data is transmitted according to the direction of the parameter:

  • In the [in] direction, the data for all nonpipe arguments is transmitted first, followed by pipe data.
  • In the [out] direction, the server sends the pipe data first. After the manager routine returns, the server transmits the nonpipe data.
  • When there are [in,out] pipe arguments combined with [in,out] non-pipe arguments, first the input data is transmitted in its entirety, as previously described. Then, the output data is transmitted as previously described.

The following restriction applies to this (MIDL 3.0) implementation of pipes: When you combine pipe types and other types in a single remote procedure call, the nonpipe parameters must have a well-defined size in order to allow the MIDL compiler to calculate the buffer size needed. For example, you cannot combine pipe parameters with a [ unique] pointer or a conformant structure, since their sizes cannot be determined at compile time.

Related topics

pipe

/Oi

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)

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

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