This project is read-only.

If You Need to Support Disconnected Queued Calls, Use netMsmqBinding

- J.D. Meier, Carlos Farre, Jason Taylor, Prashant Bansode, Steve Gregersen, Madhu Sundararajan, Rob Boucher

If you need to support disconnected queuing, use the netMsmqBinding. Queuing is provided by using the MSMQ (Microsoft Message Queuing) as a transport, which enables support for disconnected operations, failure isolation, and load leveling. You can use netMsmqBinding when the client and the service do not have to be online at the same time. You can also manage any number of incoming messages by using Load leveling. MSMQ supports failure isolation where messages can fail without affecting the processing of other messages.

The netMsmqBinding has the following characteristics:
  • It supports asynchronous, disconnected operations
  • It can only be consumed by WCF enabled clients.
  • Transport security is turned on by default, message security is also available.
  • The service can be hosted in IIS 5.0 or IIS 6.0, but it is not message activated, hence you can consider hosting in a Windows service or IIS 7.0 instead.
  • If you choose to use message security you can use certificates, username, Windows or token authentication
  • If you choose to use transport security you can only use certificates or Windows authentication

The following example shows how to configure netMsmqBinding:
<system.serviceModel>
....
    <services>
        <service behaviorConfiguration="" name="WCFServicecHost.MyService">
            ...
            <endpoint address="" binding="netMsmqBinding" bindingConfiguration=""
                name="MsmqBinding" contract="WCFServicecHost.IMyService" />
            ...
        </service>
    </services>
</system.serviceModel> 

Additional Resources

Last edited Jun 12, 2008 at 10:12 PM by prashantbansode, version 1

Comments

No comments yet.