Thanks
These limitations in Silverlight net.tcp reduce its usefulness for internet applications:
- net.tcp requires ports in the range 4502-4534. Users behind restrictive firewalls cannot make connections over those ports. However, net.tcp can still be useful as a first try, with fallback to an HTTP binding if the port is blocked. This maintains the client performance and server scalability benefits where possible.
- net.tcp does not support TLS.
References:
- MSDN: Building and Accessing Duplex Services
- The duplex story: looking at duplex communication in Silverlight - Part 3: Using Net.Tcp
- WCF net.tcp protocol in Silverlight 4
精彩评论