ASP.NET WCF Service Bindings

WCF supports different protocols for communicating with the other services and allowing access to client. This blog describes the difference between different protocols used with WCF services.

BasicHttpBinding: 
It uses HTTP transport protocol and it is of text/xml message encoding type. It does not support security. There is no reliability and also It does not support transactions.

WSHttpBinding: 
It uses HTTP/HTTPS transport protocol. It is a secure and inter-operable binding and It supports Message security. Reliability is disabled by default. It support WS- Atomic Transactions.

WSDualHttpBinding: 
It uses HTTP transport protocol and reliable messaging is enabled by default. It support WS- Atomic Transactions.

NetTcpBinding: 
It uses TCP as a transport protocol and It supports Binary Message encoding. also, It supports Transport security mode. Reliable messaging is disabled and it supports OLE Transactions.

NetPeerTcpBinding: 
It supports P2P transport protocol and it is Binary message encoding.It supports transport security mode. Reliable messaging and Transaction flow is disabled.

NetNamedPipeBinding: 
It uses NamedPipes as transport protocol and uses Binary Message Encoding. It supports Transport security mode and OLE Transactions. It is not a reliable messaging protocol.

NetMsmqBinding: 
It supports MSMQ transport , Message security mode and Binary Message encoding. It is not a reliable protocol and it does not support transactions.

MsmqIntegrationBinding: 
It also supports MSMQ transport same as NetMSMQBinding but it does not support message encoding. It supports Transport security mode whereas NetMsmqBinding supports Message security mode.

Comments

Popular posts from this blog

Email Sending through O365 using OAuth Protocol

IISRESET vs App Pool Recycling ?

Deploy .Net6.0 Web api with docker