WCF NetTCPBinding vs HttpBinding difference in data sent on wire

wcf wcf-binding nettcpbinding wshttpbinding basichttpbinding
Remotec picture Remotec · Mar 31, 2011 · Viewed 8.5k times · Source

Say I have a service exposing two end points, 1st is a NetTCPBinding the second is any flavour of HttpBinding. They both implement exactly the same service contract.

What is the difference in what is sent on the wire?

  • Using netTcp is my message still serialised to XML ? Or some binary representation of my objects?
  • In terms of what receives the messages what is the difference? Will the http endpoint only understand http commands (get/post etc) where as the nettcp end point understands something different?
  • Why is nettcp more efficient (in this case I dont need interoperability) than http - where is the overhead?

I think that in all cases, before the message is put onto the wire it will be converted to binary so, also http sits on top of tcp in networking terms - so somewhere extra is needed for http communications.

Appreciate the question is a bit vague but hopefully someone will know what I am trying to ask :)

Answer

JohnC picture JohnC · Mar 31, 2011

In WCF a particular binding does not necessarily imply a particular encoding. Various bindings can be configured to use various encodings. Net.TCP uses a binary encoding by default (MTOM I think), and HTTP uses a text/xml encoding by default.

With net.tcp your messages go sender -> net.tcp -> receiver. With HTTP they go from sender -> http -> tcp -> http -> receiver. There's an extra layer. The advantage of tcp is both of those: Both the extra layer and the default encoding.

HTTP with a binary encoding approaches net.tcp performance.

EDIT: Actually I think there may also be other optimizations in Net.TCP. It's a WCF-WCF communication scenario, so MS has control of both ends.

Related questions

netTcpBinding or wsHttpBinding

I have a WCF Service hosted as Windows Service and client is an ASP.Net application consuming WCF Service methods. In process of implementing security, I am confused over which among netTcpBinding/wsHttpBinding will be suitable for my case. Most …

Read More
Net TCP binding: The URI prefix is not recognized

This really is bugging me for a couple of hours. I created the simplest WCF service using a TCP binding. namespace WcfTcpService { public class TestTcpService : ITestTcpService { public string Hello(string name) { return "Hello, " + name + "!"; } } } namespace WcfTcpService { [ServiceContract] public interface ITestTcpService { […

Read More
Dynamically set endpoint address in wcf client (with net tcp binding)

So I'm not overly familiar with WCF and all the stuff I've googled hasn't helped me with how to achieve what I need. Sorry if this is a dumb question :) Basically there is a server app with services exposed with …

Read More