Lots of cool things about R2 in the pipeline and one of them is BizTalk’s deep integration
with WCF.
What does that mean for you? If you havent already, start looking at WCF as going
forward I believe that the majority of BizTalk solutions will be incorporating WCF
in a big way.
I’m currently writing a course for R2/WCF/WF stuff and I thought I’d jot down a table
so WCF things stick in my mind.
WCF Endpoint = Address + Contract + Binding
WCF Binding = Transport + Message Encoding
WCF Contract = Message/Data details
WCF Address = <moniker>://<server>:<Port>/<endpoint URI>
Binding Types
-
BasicHTTPBinding – Maximum interoprability through conformity to
the WS-Basic Profile 1.1 - WSHttpBinding – HTTP communication in conformity to the WS-* procotcols.
-
WSDualHttpBinding – Duplex HTTP communication, by which the receiver
of an initial message will not reply directly to the initial sender, but may transmit
any number of responses via HTTP in conformity to WS-* protocols. -
WSFederationBinding – HTTP communication, in which access to the
resources of a service can be controlled based on credentials issued by an explicitly-identified
credential provider. -
NetTCPBinding – Secure, reliable, high-performance communication
between WCF software components across the network. -
NetNamedPipeBinding – Secure, reliable, high-performance communication
between WCF s/w components on the same machine. - NetMSMQBinding – WCF communicating over MSMQ
- MsmqIntegrationBinding – WCF entities communicating via MSMQ
-
NetPeerTcpBinding – WCF entities communicating via Windows Peer-To-Peer
services
(ones that are missing at the moment – ‘Interprocess Communication Binding’ IPC, was
in the early betas…..and SQL Server Service Broker)