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

Server-side Cleanup

· 52CE 我爱测

Server-side cleanup and Remote Procedure Call (RPC).

Imagine the following scenario:

A client opens a context handle, and then either stops or loses connectivity to the server. How does the server detect that the client has failed and the context handle should be run down? There are two subscenarios: one is that the client is shut down in an orderly manner. In such case, it notifies the server that it is shutting down, and the server can clean up, including performing context run downs. If the client does not shut down in an orderly manner or it cannot notify the server, the server uses keep alives to determine whether the client is still available. On the server side, the RpcMgmtSetComTimeout function has no effect. Instead, the server uses the global per machine–keep alive setting, which defaults to approximately two hours. If the client does not respond to the server's keep alives, the connection is closed. When all connections to a given client process are closed, the server cleans up and runs down outstanding context handles.

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)

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

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