No members of this type are thread safe.
In an interactive session, the timeout period for the EndRequests 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 EndRequests 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 EndRequests method, while a user-specified for timeout for the EndRequests method is still supported for handling errors.
|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.|
|A Session object and a DurableSession object handle requests differently. A Session object may begin processing requests before the EndRequests method is called. However, a DurableSession object will not process requests until the EndRequests method is called. After the EndRequests method is called, the DurableSession object will commit the requests to the message queue.|
|BrokerClient.EndRequests ()||Informs the broker that this instance of the BrokerClient class is finished sending request messages and that the broker should commit all request messages, subject to the default timeout period.|
|BrokerClient.EndRequests (Int32)||Informs the broker that this instance of the BrokerClient class is finished sending request messages and that the broker should commit all request messages, subject to the specified timeout period.|