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

Causal Ordering of Asynchronous Calls

· 52CE 我爱测

In an asynchronous RPC application, it is possible for a client thread to make a second asynchronous call on a binding handle before an earlier call made on that handle has completed.

In an asynchronous RPC application, it is possible for a client thread to make a second asynchronous call on a binding handle before an earlier call made on that handle has completed. The RPC run-time library handles this situation as follows:

  • The asynchronous RPC mechanism guarantees that asynchronous calls made on the same binding handle, on the same thread, at the same security level, are dispatched in the order they were made. Actual execution of the calls may occur out of order.
  • As with synchronous calls, asynchronous remote procedure calls from different client threads execute simultaneously.
  • If an asynchronous call from a client application is followed by one or more synchronous calls, the asynchronous call can execute while the synchronous calls are executing. Regardless of the status of the asynchronous call, the synchronous calls are executed in the order in which they are received by the server.
  • If a client application selects noncausal ordering for a particular binding handle, it disables serialization for that handle. Applications enable noncausal ordering by calling RpcBindingSetOption with the Option parameter set to RPC_C_OPT_BINDING_NONCAUSAL and the OptionValue parameter set to TRUE. For details, see Binding Option Constants.

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)

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

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