Last post Sep 15, 2016 05:42 AM by Chris Zhao
Sep 14, 2016 12:01 AM|dealkk|LINK
I have a service wsdl that I can browse using url :
http://myserver/myservices?wsdl , that look like this
<wsdl: definition name = "abc"
<wsdl:import namespace="http://tempuri.org" location=http://myserver/myservices?wsdl />
<wsdl:binding name="NetTcpBinding_Service" type="Service"> <wsp:PolicyReference URI="#NetTcpBinding_Service_policy" />
<soap12:binding transport="http://schemas.microsoft.com/soap/tcp" />
When I look at it, it look like nettcp, but how does it expose as http? is it because http wrap around nettcp?
Sep 15, 2016 05:42 AM|Chris Zhao|LINK
When we browser an address like http://xxx.xx.x.x and not tcp://xxx.xx.x.x. i.e. it's using the http protocol, http needs to send some configuration info with each transfer. In WCF, the HTTP transport binding is optimized for interoperability with legacy
non-WCF systems. If all communicating parties are using WCF, the TCP-based or named pipes-based bindings are faster.
How to Create Basic HTTP Binding in WCF
Host WCF in a Windows Service Using TCP