Here is a quick aide-mémoire about WCF bindings. This table is basically taken from the MSDN documentation for WCF bindings in .Net 3.5 with a few extra notes here and there.
Binding | Configuration Element | Description |
A binding that is suitable for communicating with WS-Basic Profile conformant Web services, for example, ASP.NET Web services (ASMX)-based services. This binding uses HTTP as the transport and text/XML as the default message encoding. | ||
A secure and interoperable binding that is suitable for non-duplex service contracts. Supports the latest interoperable web service standards (WS*) and is compatible with more recent web service stacks. * | ||
A secure and interoperable binding that is suitable for duplex service contracts or communication through SOAP intermediaries. | ||
A secure and interoperable binding that supports the WS-Federation protocol that enables organizations that are in a federation to efficiently authenticate and authorize users. A web service binding that supports WS* as it relates to federated and single sign-on security scenarios. * | ||
A secure and optimized binding suitable for cross-machine communication between WCF applications. A connection-oriented binding for communications across process and machine boundaries over TCP. * | ||
A secure, reliable, optimized binding that is suitable for on-machine communication between WCF applications. A connection-oriented binding for communications on the same machine over named-pipes. * | ||
A queued binding that is suitable for cross-machine communication between WCF applications. Supports durable reliable messaging over MSMQ. * | ||
A binding that enables secure, multiple machine communication. Supports peer-to-peer and broadcast communications. * | ||
A binding that is suitable for cross-machine communication between a WCF application and existing Message Queuing applications. Supports integration with legacy MSMQ components. * | ||
A binding that is suitable for communicating with WS-Basic Profile conformant Web services that enables HTTP cookies to be used to exchange context. | ||
A secure and optimized binding suitable for cross-machine communication between WCF applications that enables SOAP headers to be used to exchange context. | ||
A binding used to configure endpoints for WCF Web services that are exposed through HTTP requests instead of SOAP messages. | ||
A secure and interoperable binding that is suitable for non-duplex service contracts that enables SOAP headers to be used to exchange context. |
* pp160-161, Learning WCF, Michelle Leroux Bustamonte