When creating a WCF Service with NetTcpBinding, use endpoint "localhost" or machine's host name?
        Posted  
        
            by Elan
        on Stack Overflow
        
        See other posts from Stack Overflow
        
            or by Elan
        
        
        
        Published on 2009-11-04T21:18:57Z
        Indexed on 
            2010/04/27
            9:53 UTC
        
        
        Read the original article
        Hit count: 415
        
I have a WCF service that uses the NetTcpBinding and is running within a Windows service. Remote clients connect to this service. So far, I have defined the endpoint to use "localhost".
If the host machine has multiple network adapters, will it receive messages on all adapters?
Would it be better to assign the machine's host name to the endpoint instead of "localhost"?
What are the advantages/disadvantages?
© Stack Overflow or respective owner