This project is read-only.

Choose the Right Binding for Your Scenario

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

Use the following recommendations as a rule of thumb when choosing a binding option. You can fine tune your selection based on your unique needs and your infrastructure limitations.
  • If your service needs to support legacy clients that expect an ASMX web service, consider using the basicHttpBinding. basicHttpBinding does not implement any security by default, if you require message or transport security you should configure it explicitly on this binding. Use basicHttpBinding to expose endpoints that are able to communicate with ASMX-based Web services and clients and other services that conform to the WS-I Basic Profile 1.1. When configuring transport security, basicHttpBinding defaults to no credentials just like a classic ASMX web service. basicHttpBinding allows you to host your service in II5 or IIS6.
  • If your service will be called by clients over the Internet, consider using the wsHttpBinding. wsHttpBinding is a good choice for Internet scenarios in which you do not have to support legacy clients which expect an ASMX web service. If you do need to support legacy clients, consider using basicHttpBinding instead. WsHttpBinding allows you to host your service in II5 or IIS6.
  • If you need to support clients within your intranet, consider using netTcpBinding. netTcpBinding is a good choice for the intranet scenario if transport performance is important to you and it is ok to host the service in a Windows service instead of in IIS. The netTcpBinding uses the TCP protocol and provides full support for message security, transactions, and reliability. Use this binding when you want to provide a secure and reliable binding environment for .NET-to-.NET cross-machine communication. netTcpBinding, you can host in IIS 7.0 or a Windows Service. You can also host in IIS 6.0, but you must first have to activate the host W3wp process, before using the service.
  • If you need to support WCF clients on the same machine as your service, consider using the netNamedPipeBinding. The netNamedPipeBinding provides a secure and reliable binding environment for cross-process, same machine communication. Use this binding when you want to make use of the NamedPipe protocol and provide full support for SOAP security, transactions, and reliability. netNamedPipeBinding, you can host in IIS 7.0 or a Windows Service. You can also host in IIS 6.0, but you must first have to activate the host W3wp process, before using the service.
  • 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. netMsmqBinding, you can host in IIS 7.0 or a Windows Service. You can also host in IIS 6.0, but you must first have to activate the host W3wp process, before using the service.
  • If you need to support a duplex service, use wsDualHttpBinding. A duplex service is a service that uses duplex message patterns which provides the ability for a service to communicate back to the client via a callback. You can also use this binding to support communication via SOAP intermediaries.

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

Comments

No comments yet.