What is netNamedPipeBinding in WCF ?
NetNamedPipeBinding is the best mechanism for interprocess communication. With netNamedPipeBinding the security can be achieved only through transport level security as it does not support message level security. However messages are secured as only the same machine can call the service operations.
The reason netNamedPipeBinding is the best mechanism because it gives you the default security .
NetTcpBinding best when clients are only from intranet.
The reason netNamedPipeBinding is the best mechanism because it gives you the default security .
NetTcpBinding best when clients are only from intranet.
======= in web.config of service ======
<services>
<service
name="NorthwindServices.CustomerService"
behaviorConfiguration="ServiceBehavior">
<service
name="NorthwindServices.CustomerService"
behaviorConfiguration="ServiceBehavior">
<host>
<baseAddresses>
<add baseAddress="net.pipe://localhost/NorthwindServices/" />
</baseAddresses>
</host>
<baseAddresses>
<add baseAddress="net.pipe://localhost/NorthwindServices/" />
</baseAddresses>
</host>
<endpoint address="CustomerService"
binding="netNamedPipeBinding"
contract="NorthwindServices.ICustomer" />
binding="netNamedPipeBinding"
contract="NorthwindServices.ICustomer" />
<endpoint address="CustomerService/mex"
binding="mexNamedPipeBinding"
contract="IMetadataExchange" />
binding="mexNamedPipeBinding"
contract="IMetadataExchange" />
</service>
</services>
</services>
Comments
Post a Comment