简体   繁体   中英

WCF NetTcpBinding in IIS

If the net.tcp Binding uses TCP as a transport protocol - how does this actually work in IIS, given that IIS in itself is a Web Server?

Just trying to understand how the technology works.

Since 7.0, IIS supports Windows Process Activation Service (WAS). WAS is a fundamental underlying component of IIS 7.0 that makes it possible to host WCF services beyond HTTP.

It allows the use of transport protocols other than HTTP, such as TCP, named pipes, and MSMQ (previously, IIS 6.0 only allowed the use of HTTP).

A complete explanation is available here .

IIS is not just a "web" server; it is designed to handle several protocols implemented on the TCP/IP stack.

net.tcp and HTTP are both implemented at the "Application Layer" of the Internet Protocol Suite , so it's no surprise that a server that can handle one can be designed to handle the other. BTW, the transport mechanism for HTTP is TCP as well.

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM