WCF Configuration Notes

For addresses and bindings in WCF, you need to add a little bit more.

the transport protocols supported in WCF include HTTP, TCP, peer network (peer), IPC (internal process communication based on named Pipes), and MSMQ (Microsoft Message Queuing), each of which corresponds to one address type:

• HTTP Address: http://localhost:8080/
• TCP Address: net.tcp://localhost:8080/
• IPC Address: net.pipe://localhost/(for cross-process, cannot be used in different machine rooms)
• MSMQ Address: net.msmq://localhost/
• Peer network address: net.p2p://localhost/

The bindings provided in WCF are:

• BasicHttpBinding: The simplest type of binding, typically used for Web Services. Using the HTTP protocol, the Text/xml encoding method.
• Wshttpbinding: More secure than basichttpbinding, typically used for Non-duplex service communication.
• Wsdualhttpbinding: It supports duplex types of services compared to Wshttpbinding.
• WSFederationHttpBinding: Supports Ws-federation Secure communication protocol.
• NetTcpBinding: The most efficient and safe way to communicate across machines.
• NetNamedPipeBinding: Secure, reliable and efficient communication mode for stand-alone service.
• NetMsmqBinding: Use Message Queuing to communicate between different machines.
• NetPeerTcpBinding: Communicate with multiple machines using peer-to-peer protocols.
• MsmqIntegrationBinding: Use an existing Message Queuing system for cross-machine communication. such as MSMQ.

  ------Weak and weak divider lines-----

OK, with the foundation above, let the WCF storm come violently. Do a multi-service, multiple-point example.

WCF Configuration Notes