This project is read-only.

Know your binding options

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

Know your binding options and choose the most appropriate for your scenario. Knowing your binding options enables you to design more reliable and secure WCF application.

For choosing a binding option, following can used as thumb of rule, they are recommendations and not compulsions, you can fine tune your selection on need basis and infrastructure limitations.
  • If you need to support non WCF clients which are expecting legacy ASMX web service, use basicHttpBinding.
  • If you need to support non WCF client which understands the WS* stack, use wsHttpBinding.
  • If you need to support remote WCF clients within the intranet use netTcpBinding.
  • If you need to support local WCF clients use netNamedPipeBinding.
  • If you need to support WCF clients, which needs offline or disconnected interactions use netMsmqBinding.
  • If you need to support non WCF legacy MSMQ client use MsmqIntegrationBinding

Last edited Apr 24, 2008 at 12:06 AM by prashantbansode, version 1

Comments

ronjacobs May 19, 2008 at 2:38 AM 
If you need to support non WCF clients without a SOAP stack use webHttpBinding and WebGet / WebInvoke for a REST style API