title: WCF HTTP and NamedPipe service
body: <p>I'm creating a WCF service which, at the moment, exposing a number of contracts using a basicHttpBinding. However, I now want to use the service locally on the same machine, and a netNamedPipeBinding seems more appropriate in terms of performance. For that reason, I want to expose the service using a named pipe and HTTP.</p>
  
  <p>At the moment I'm doing this with the following configuration:</p>
  
  <pre><code>&lt;service name="WCFService.MyService" behaviorConfiguration="serviceBehaviour"&gt;
      &lt;host&gt;
        &lt;baseAddresses&gt;
          &lt;add baseAddress="http://localhost:8080/MyService" /&gt;
          &lt;add baseAddress="net.pipe://localhost/MyService" /&gt;
        &lt;/baseAddresses&gt;
      &lt;/host&gt;
  
      &lt;endpoint address="calculator" binding="basicHttpBinding" contract="WCFService.ICalculatorService" /&gt;
      &lt;endpoint address="database" binding="basicHttpBinding" contract="WCFService.IDatabaseService" /&gt;
  &lt;/service&gt;
  </code></pre>
  
  <p>This appears to work fine, but on closer inspection the endpoints are still using the basicHttpBinding. This works, but I get the impression it's creating unnecessary overhead. </p>
  
  <p>Do I need to create an endpoint for each contract, and each binding type (i.e. basicHttpBinding and netNamedPipeBinding) or am I going about this completely wrong? </p>
  
  <p>(If it's not clear, I'm fairly new to WCF!)</p>