title: WCF TCP binding or Named pipes for grid computing?
body: <p>I'm building a distributed system. There are several applications (some are .Net based (C#), others are C++ based (NOT C++/CLI!)). 
  Those apps will be installed on each computer in cluster (currently Windows-driven).
  On local PC I use for IPC: MemoryMappedFiles for C# apps, Shared Memory for C++ apps, Named Pipes for IPC between C# and C++.
  Over internet I use WCF TCP binding, using C# apps as bridges for C++ apps.</p>
  
  <p>What would be better to use for LAN communication? MPICH2, it seems, use TCP...
  Are typical named pipes quicker than WCF TCP binding with optimizations (disabled security, etc.)? The messages will be extremely large, mostly of double type. WCF is extremely convenient in my situation (all mathematical methods are simply contracts), but it's performance is a question.</p>