Monday, 5 December 2016

Understanding WCF Bindings

Binding describes that how a client will communicate with wcf service. It tells that what protocol will be used to communicate, as WCF supports various protocols like HTTP, TCP, MSMQ, Named Pipes.

Binding determine transport protocol i.e. TCP, HTTP, message exchange format i.e. plain text, xml

You may go through to my earlier blogs to know about ABC of WCF

Below are the list of bindings supported by WCF.

BasicHttpBinding
WSHttpBinding
WSDualHttpBinding
WSFederationHttpBinding
NetTcpBinding
NetNamedPipeBinding
NetMsmqBinding
NetPeerTcpBinding
MsmgIntegrationBinding

Lets discuss all bindings one by one.

BasicHttpBinding : Basic web service communication, no security.

WSHttpBinding : It is a SOAP based used for secure, reliable , inter-operable system. Similar to  BasicHttpBinding with more web service features. 

WSDualHttpBinding : With duplex contract i.e. allows services and clients to send and receive messages.

WSFederationHttpBinding

NetTcpBinding : Provide secure and reliable binding for .Net to .Net cross machine communication. NetTcpBinding generates a run time communication stack by default.

NetNamedPipeBinding : Communication is possible only on same machine, supports duplex contracts.

NetMsmqBinding : Communication between applications by using queuing.
MSMQ stands for Microsoft Message Queue server. MSMQ assure you for very less chances of loosing message. MSMQ works on FIFO principal i.e. the message comes first will be released first.MSMQ handle requests from multiple clients, it maintain the queue of all requests.

NetPeerTcpBinding : Communication between computers across peer to peer.

MsmqIntegrationBinding : Direct communication with MSMQ system.

No comments:

Post a Comment