The RPC library uses the binding time-out constants to specify the relative amount of time that should be spent to establish a binding to the server before giving up. The timeout can be enabled with a call to the RpcMgmtSetComTimeout function. The following list contains the valid time-out values.
| Constant/value | Description |
|---|---|
| RPC_C_BINDING_INFINITE_TIMEOUT 10 | Keeps trying to establish communications forever. |
| RPC_C_BINDING_MIN_TIMEOUT 0 | Tries the minimum amount of time for the network protocol being used. This value favors response time over correctness in determining whether the server is running. |
| RPC_C_BINDING_DEFAULT_TIMEOUT 5 | Tries an average amount of time for the network protocol being used. This value gives correctness in determining whether a server is running and gives response time equal weight. This is the default value. |
| RPC_C_BINDING_MAX_TIMEOUT 9 | Tries the longest amount of time for the network protocol being used. This value favors correctness in determining whether a server is running over response time. |
Remarks
The values in the preceding table are not in seconds. These values represent a relative amount of time on a scale of zero to 10. For more information on avoiding communication delays, refer to Preventing Client-side Hangs.
Requirements
| Requirement | Value |
|---|---|
| Minimum supported client | Windows 2000 Professional [desktop apps only] |
| Minimum supported server | Windows 2000 Server [desktop apps only] |
| Header | Rpcdce.h |
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.
