1. Bind the configuration of the communication channel
2. Binding defines the communication protocol between the client and the server (specific functions)
A. Transmission Protocol
B. Message Encoding
C. Security and reliability of messages and transactions
Transmission Protocol: HTTP, TCP, Named pipe (Named Pipes), MSMQ
And provides custom support for UDP or SMTP.
Other binding protocols:
1. Security: mutual authentication certificate (X.509) message protection
2. Reliable messages
3. transaction support
4. Ability to use custom binding protocol for extension
Channel (channels ):
1. The channel stack sends or accepts messages between each communication endpoint.
The client proxy is a channel built from the client binding configuration.
Servicehost exposes the channel listener for each endpoint Based on the configuration bound to the service.
A channel stack is composed of binding elements. It can be said that a channel stack is composed of several different binding elements.
Binding is composed of binding elements and is related to the endpoint.
Standard binding:
1. predefined binding elements
2. Provides the default value for HTTP, TCP, named pipe, or MSMQ communication.
3. The configuration can be modified.
Custom binding:
1. Fully customized set of bound Elements
2. When the standard binding cannot meet the requirements
The main bindings include the following:
1. basichttpbinding
2. wshttpbinding
3. wsdualhttpbinding
4. wsfederationhttpbinding
5. netnamedpipebinding
6. nettcpbinding
7. netpeertcpbinding
8. netmsmqbinding
9. msmqintegrationbinding
Web Service binding:
1. basichttpbinding is compatible with soap1.1
2. wshttpbinding
3. wsdualhttpbinding
4. wsfederationhttpbinding is applicable to scenarios of joint security and single point of login (SSO ).
Cross-process/host binding:
5. netnamedpipebinding Used for calls within processes or on the same host
6. nettcpbinding is used for the same host or cross-host call.
7. netpeertcpbinding is used for point messages of the same host or cross-host point.