Types of Binding:
1. BasicHttpBinding
2. WSHttpBinding
3. W2007HttpBinding
4. WSDualHttpBinding
5. WSFederationBinding
6. WS2007FederationBinding
7. NetTcpBinding
8. NetNamedPipeBinding
9. NetPeerBinding
10. NetMsmqBinding
11. MsmqIntegrationBinding
Each binding having following properties:
1. Binding Class Properties
2. Common Binding Properties.
3. Non-Shared Properties.
4. Customize Binding Properties.
Can any one explain binding and their properties. Comparison binding and limitation.
Loading
Hemant KumarPosted Sep 26, 2011, 4:44 AM
WCF also allows you to define your own custom bindings.
Class name
Description
Transport
Message encoding
Security
BasicHttpBinding
A binding that is suitable for communication with WS-Basic Profile conformant Web Services like ASMX-based services. This binding uses HTTP as the transport and Text/XML as the message encoding.
HTTP
Text
None
WSHttpBinding
A secure and interoperable binding that is suitable for non-duplex service contracts.
HTTP
Text
Message
WSDualHttpBinding
A secure and interoperable binding that is suitable for duplex service contracts or communication through SOAP intermediaries.
HTTP
Text
Message
WSFederationHttpBinding
A secure and interoperable binding that supports the WS-Federation protocol, enabling organizations that are in a federation to efficiently authenticate and authorize users.
HTTP
Text
Message
NetTcpBinding
A secure and optimized binding suitable for cross-machine communication between WCF applications
TCP
Binary
Transport
NetPeerTcpBinding
A binding that enables secure, multi-machine communication.
P2P
Binary
Transport
NetNamedPipesBinding
A secure, reliable, optimized binding that is suitable for on-machine communication between WCF applications.
Named Pipes
Binary
Transport
NetMsmqBinding
A queued binding that is suitable for cross-machine communication between WCF applications.
MSMQ
Binary
Message
MsmqIntegrationBinding
A binding that is suitable for cross-machine communication between a WCF application and existing MSMQ applications.
MSMQ
doesn't use a WCF message encoding – instead it lets you choose a pre-WCF serialization format
Transport