I have read a post from Tomasz Janczuk about Silverlight 4 and Net.Tcp Binding. I have an application that has a huge traffic of information. According to Tomasz net.tcp bindig is, by far, faster then the other bindings.
There is also a security restriction since, at least now, Net.TCP in Silverlight will not have Transport level security.
The problem is that he said that the practical use of the protocol is constrained to intranet environments and I my application must be hosted in a public server.
Is this a real restriction or only a suggested one ????
Will Silverlight restrict the address ????
Can anyone give me mor information and help me to decide.
Thanks in advance
WCF net.tcp communication protocol in Silverlight is subject to the same TCP port range restrictions as sockets: Silverlight applications can only attempt to communicate with TCP ports in the 4502-4534 range (as described at http://msdn.microsoft.com/en-us/library/cc645032(VS.95).aspx). While there is nothing that prevents hosting of such applications or the WCF net.tcp services they communicate with on a public server, in the practical internet deployments communication is unlikely to be successful due to the configuration of the firewalls beyond the control of the application developer. Given the port restrictions, the WCF net.tcp protocol in Silverlight is practically constrained to intranet deployments where the networking environment can be more freely adjusted.
Check this for details and a working sample (silvelight 5):
- Edited by Arshdeep Virdi Friday, July 06, 2012 5:53 AM