System.ServiceModel 4.0.0.0

In some cases it may be more efficient for a binding to process messages with the synchronous or methods. A class can optionally implement to indicate to callers that this is preferred.

If a binding does not implement , the indigo1 Service Model Runtime layer defaults to using the asynchronous versions of the Receive and Request methods. If a binding does implement , the indigo2 Service Model Runtime layer checks the value of and uses that to determine whether to call the synchronous versions of the these methods ( or ) or the asynchronous versions ( and or and . If is implemented by the binding and returns true from the property, it is recommended that you use the synchronous and methods to receive messages from the channel. If the binding does not implement or returns false from the property, it is recommended that you use the asynchronous and or and methods.

Regardless of the value returned by the property, all bindings must still provide valid implementations of both the synchronous and asynchronous versions of the Receive methods for the specific channel types implemented. For more information about implementing custom channels, see Developing Channels.

Defines the optional contract that a binding can implement to specify whether incoming requests are handled synchronously or asynchronously by the service.

- Property
  4.0.0.0
  System.Boolean To be added.

  The standard (system-provided) bindings provided by indigo1 have implemented this interface and in some cases override the default value to process incoming messages synchronously.

  Gets a value that indicates whether incoming requests can be handled more efficiently synchronously or asynchronously.