BrokerClient.Flush Method

Informs the broker that it should commit all request messages.

No members of this type are thread safe.

In an interactive session, the timeout period for the Flush method is affected by throttling if the client sends more requests than the value specified for the messageThrottleStartThreshold attribute in the service configuration file specifies. If throttling is enabled, the Flush method does not time out until the service operation timeout is reached. Thus, the same service operation timeout is used for throttling for the SendRequest and Flush method, while a user-specified for timeout for the Flush method is still supported for handling errors.

If throttling is not enabled, the timeout value specified for the Flush method or the default timeout period for Flush applies.

noteNote
The difference between the Flush method and the EndRequests method: The Flush method commits all pending request messages, and allows further request messages to be sent after the Flush method was called. The EndRequests method commits all pending request messages, and does not allow further request messages to be sent.

This method was introduced in Windows HPC Server 2008 R2 with Service Pack 1 (SP1) and is not supported in previous versions.

NameDescription
BrokerClient.Flush ()Informs the broker that it should commit all request messages, subject to the default timeout period.
BrokerClient.Flush (Int32)Informs the broker that it should commit all request messages, subject to the specified timeout period.




Build Date:

2013-04-22
Show: