<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/'><id>tag:blogger.com,1999:blog-2987032012497124857.post5581690029207099111..comments</id><updated>2010-03-11T12:52:42.269-08:00</updated><title type='text'>Comments on Tomek on Software: WCF net.tcp protocol in Silverlight 4</title><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://tomasz.janczuk.org/feeds/5581690029207099111/comments/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default'/><link rel='alternate' type='text/html' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html'/><author><name>Tomasz Janczuk</name><uri>http://www.blogger.com/profile/14273379892104866795</uri><email>tomasz@janczuk.org</email></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>21</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-2987032012497124857.post-6132107224236096658</id><published>2010-03-11T12:52:42.216-08:00</published><updated>2010-03-11T12:52:42.216-08:00</updated><title type='text'>Tomasz, is there any reason an approach like this ...</title><content type='html'>Tomasz, is there any reason an approach like this wouldn&amp;#39;t work?&lt;br /&gt;&lt;br /&gt;- On the server, expose your WCF service using both Net.TCP and PollingDuplexHttpBinding.&lt;br /&gt;- On the client, try to open a connection to the web service using Net.TCP.&lt;br /&gt;- If that succeeds, use Net.TCP.&lt;br /&gt;- If that fails, fallback to the PollingDuplexHttpBinding.&lt;br /&gt;&lt;br /&gt;That&amp;#39;s the approach we&amp;#39;re currently taking, and it seems to be working.  Any reason why it wouldn&amp;#39;t, or any reason why we shouldn&amp;#39;t?</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/6132107224236096658'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/6132107224236096658'/><link rel='alternate' type='text/html' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html?showComment=1268340762216#c6132107224236096658' title=''/><author><name>Ken Smith</name><uri>http://www.blogger.com/profile/09031647503349727336</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html' ref='tag:blogger.com,1999:blog-2987032012497124857.post-5581690029207099111' source='http://www.blogger.com/feeds/2987032012497124857/posts/default/5581690029207099111' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-2987032012497124857.post-183521693361366121</id><published>2010-02-10T20:15:23.546-08:00</published><updated>2010-02-10T20:15:23.546-08:00</updated><title type='text'>A cross-platform communications protocol that supp...</title><content type='html'>A cross-platform communications protocol that supports real call-backs and that works across the Internet and firewalls is ICE (http://zeroc.com).&lt;br /&gt;&lt;br /&gt;They have Silverlight 2/3 support as well.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/183521693361366121'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/183521693361366121'/><link rel='alternate' type='text/html' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html?showComment=1265861723546#c183521693361366121' title=''/><author><name>Karl_W</name><uri>http://kwaclaw.myopenid.com/</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html' ref='tag:blogger.com,1999:blog-2987032012497124857.post-5581690029207099111' source='http://www.blogger.com/feeds/2987032012497124857/posts/default/5581690029207099111' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-2987032012497124857.post-4487394211221942340</id><published>2010-02-05T13:41:04.695-08:00</published><updated>2010-02-05T13:41:04.695-08:00</updated><title type='text'>Is it possible to have data validation attributes ...</title><content type='html'>Is it possible to have data validation attributes in the classes on the server side and when adding a service reference to the server to have the classes generated with the data annotations on them?</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/4487394211221942340'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/4487394211221942340'/><link rel='alternate' type='text/html' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html?showComment=1265406064695#c4487394211221942340' title=''/><author><name>Florin</name><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html' ref='tag:blogger.com,1999:blog-2987032012497124857.post-5581690029207099111' source='http://www.blogger.com/feeds/2987032012497124857/posts/default/5581690029207099111' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-2987032012497124857.post-6786267167548398775</id><published>2010-02-02T10:16:04.106-08:00</published><updated>2010-02-02T10:16:04.106-08:00</updated><title type='text'>Florin, you are right - polling duplex protocol is...</title><content type='html'>Florin, you are right - polling duplex protocol is the way to go on the public internet.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/6786267167548398775'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/6786267167548398775'/><link rel='alternate' type='text/html' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html?showComment=1265134564106#c6786267167548398775' title=''/><author><name>Tomasz Janczuk</name><uri>http://www.blogger.com/profile/14273379892104866795</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='08472674204894008885'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html' ref='tag:blogger.com,1999:blog-2987032012497124857.post-5581690029207099111' source='http://www.blogger.com/feeds/2987032012497124857/posts/default/5581690029207099111' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-2987032012497124857.post-9015424997446135742</id><published>2010-02-02T06:10:16.216-08:00</published><updated>2010-02-02T06:10:16.216-08:00</updated><title type='text'>So if I want to deploy a Silverlight 4 app which w...</title><content type='html'>So if I want to deploy a Silverlight 4 app which wants to take advantage of a duplex wcf service over the web, I would need to expose the wcf service through a PollingDuplexHttpBinding endpoint? (because I cannot rely that everyone has the tcp outgoing port allowed - 4502-4534)</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/9015424997446135742'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/9015424997446135742'/><link rel='alternate' type='text/html' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html?showComment=1265119816216#c9015424997446135742' title=''/><author><name>Florin</name><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html' ref='tag:blogger.com,1999:blog-2987032012497124857.post-5581690029207099111' source='http://www.blogger.com/feeds/2987032012497124857/posts/default/5581690029207099111' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-2987032012497124857.post-1149311287439517544</id><published>2010-01-14T13:32:09.386-08:00</published><updated>2010-01-14T13:32:09.386-08:00</updated><title type='text'>SCollard, a net.tcp WCF channel maps to a single u...</title><content type='html'>SCollard, a net.tcp WCF channel maps to a single underlying TCP connection. This means that messages client sends over an instance of a net.tcp WCF channel will always reach the same instance of the backend service despite there being an NLB between them. If the net.tcp WCF channel instance is closed or faulted and subsequently recreated by the client, a different backend server may be used to serve the client in the absence of NLB affinity. So the key question is whether your application requires or relies on client affinity to any resources maintained by the server side with lifetime exceeding the lifetime of a net.tcp WCF channel. If you are building a pub\sub system, the question translates to whether your subscriptions are durable or not. If the answer is yes, you may have to look at mechanisms to share the durable state across backends, and Velocity is one technology that can speed it up.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/1149311287439517544'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/1149311287439517544'/><link rel='alternate' type='text/html' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html?showComment=1263504729386#c1149311287439517544' title=''/><author><name>Tomasz Janczuk</name><uri>http://www.blogger.com/profile/14273379892104866795</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='08472674204894008885'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html' ref='tag:blogger.com,1999:blog-2987032012497124857.post-5581690029207099111' source='http://www.blogger.com/feeds/2987032012497124857/posts/default/5581690029207099111' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-2987032012497124857.post-8280214983311627998</id><published>2010-01-14T13:15:09.196-08:00</published><updated>2010-01-14T13:15:09.196-08:00</updated><title type='text'>Would the net.tcp duplex for Sl4 work in the follo...</title><content type='html'>Would the net.tcp duplex for Sl4 work in the following scenario?&lt;br /&gt;&lt;br /&gt;- Intranet with necessary ports opened&lt;br /&gt;- WCF services layer on redundant servers behind NLB without a guarantee of backend affinity&lt;br /&gt;- Subscriptions kept in Distributed Cache (Velocity)&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;When a server goes down what happens as the connection is made to another server through NLB?</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/8280214983311627998'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/8280214983311627998'/><link rel='alternate' type='text/html' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html?showComment=1263503709196#c8280214983311627998' title=''/><author><name>SCollard</name><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html' ref='tag:blogger.com,1999:blog-2987032012497124857.post-5581690029207099111' source='http://www.blogger.com/feeds/2987032012497124857/posts/default/5581690029207099111' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-2987032012497124857.post-6302545422018210332</id><published>2010-01-06T14:54:18.626-08:00</published><updated>2010-01-06T14:54:18.626-08:00</updated><title type='text'>Yes, net.tcp is subject to the same cross-domain s...</title><content type='html'>Yes, net.tcp is subject to the same cross-domain security concerns as http, with the mitigation being the cross-domain policy file. Is there anthing specific you would want to do over port 808?</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/6302545422018210332'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/6302545422018210332'/><link rel='alternate' type='text/html' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html?showComment=1262818458626#c6302545422018210332' title=''/><author><name>Tomasz Janczuk</name><uri>http://www.blogger.com/profile/14273379892104866795</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='08472674204894008885'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html' ref='tag:blogger.com,1999:blog-2987032012497124857.post-5581690029207099111' source='http://www.blogger.com/feeds/2987032012497124857/posts/default/5581690029207099111' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-2987032012497124857.post-469265043338959090</id><published>2010-01-04T20:30:26.624-08:00</published><updated>2010-01-04T20:30:26.624-08:00</updated><title type='text'>It is not as much a requirement as a restriction i...</title><content type='html'>It is not as much a requirement as a restriction imposed by typical environments at the internet scale. If you deploy a service that accepts TCP connections in the specified port range, the firewall of your server and the network it is connected to (e.g. your company&amp;#39;s network) must explicitly allow incoming connections on these ports. Next, client side environment must be configured to allow outgoing connections on this port, which in a general internet case is not a property that can be assumed as a default. If the default client configuration does not allow outgoing connections, client&amp;#39;s must be aware of the limitation, knowledgeable and able to change it, and above all willing to do so, none of which can be safely assumed about an average user of the public internet. As such, the deployment of net.tcp based services is in practice limited to networks that are more tightly controlled.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/469265043338959090'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/469265043338959090'/><link rel='alternate' type='text/html' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html?showComment=1262665826624#c469265043338959090' title=''/><author><name>Tomasz Janczuk</name><uri>http://www.blogger.com/profile/14273379892104866795</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='08472674204894008885'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html' ref='tag:blogger.com,1999:blog-2987032012497124857.post-5581690029207099111' source='http://www.blogger.com/feeds/2987032012497124857/posts/default/5581690029207099111' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-2987032012497124857.post-1264837631325864171</id><published>2010-01-02T18:01:04.750-08:00</published><updated>2010-01-02T18:01:04.750-08:00</updated><title type='text'>I don't understand the intranet and firewall requi...</title><content type='html'>I don&amp;#39;t understand the intranet and firewall requirements.&lt;br /&gt;&lt;br /&gt;If I build and deploy a WCF server that uses the required port range, and then deploy on a public web site a silverlight 4 app that talks to the WCF server, then are you saying that no one will be able to hit the service without messing with their firewall?&lt;br /&gt;&lt;br /&gt;Is it their windows firewall on their own computer or is it their home routers or does it have something to do with NAT (Network Address Translation)?  Why wouldn&amp;#39;t the silverlight app be able to initiate a duplex tcp connection with the server like anything else?</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/1264837631325864171'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/1264837631325864171'/><link rel='alternate' type='text/html' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html?showComment=1262484064750#c1264837631325864171' title=''/><author><name>Livingston</name><uri>http://www.blogger.com/profile/01277834452690369531</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html' ref='tag:blogger.com,1999:blog-2987032012497124857.post-5581690029207099111' source='http://www.blogger.com/feeds/2987032012497124857/posts/default/5581690029207099111' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-2987032012497124857.post-7114561801738293224</id><published>2009-12-29T12:44:21.546-08:00</published><updated>2009-12-29T12:44:21.546-08:00</updated><title type='text'>Falguni, there are no plans to remove port restric...</title><content type='html'>Falguni, there are no plans to remove port restrictions in the near future. The restrictions have been put in place for security reasons. Aaron Oneal has a great write-up about the rationale of the port restrictions at http://blogs.msdn.com/ncl/archive/2009/06/23/why-does-silverlight-have-a-restricted-port-range-for-sockets.aspx. What is your scenario that requires access to a port outside of this range?</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/7114561801738293224'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/7114561801738293224'/><link rel='alternate' type='text/html' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html?showComment=1262119461546#c7114561801738293224' title=''/><author><name>Tomasz Janczuk</name><uri>http://www.blogger.com/profile/14273379892104866795</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='08472674204894008885'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html' ref='tag:blogger.com,1999:blog-2987032012497124857.post-5581690029207099111' source='http://www.blogger.com/feeds/2987032012497124857/posts/default/5581690029207099111' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-2987032012497124857.post-4670970777233496291</id><published>2009-12-27T22:21:07.721-08:00</published><updated>2009-12-27T22:21:07.721-08:00</updated><title type='text'>Is there any plan to remove port restrictions in n...</title><content type='html'>Is there any plan to remove port restrictions in near future??</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/4670970777233496291'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/4670970777233496291'/><link rel='alternate' type='text/html' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html?showComment=1261981267721#c4670970777233496291' title=''/><author><name>Falguni</name><uri>http://www.blogger.com/profile/10789340222964930278</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html' ref='tag:blogger.com,1999:blog-2987032012497124857.post-5581690029207099111' source='http://www.blogger.com/feeds/2987032012497124857/posts/default/5581690029207099111' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-2987032012497124857.post-9192821396136462852</id><published>2009-12-11T19:42:30.658-08:00</published><updated>2009-12-11T19:42:30.658-08:00</updated><title type='text'>Fantastic article Tomasz!  I greatly appreciate th...</title><content type='html'>Fantastic article Tomasz!  I greatly appreciate the performance metrics.  Instead of theorizing you actually quantify and compare performance.  Thank-you. -Shaun</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/9192821396136462852'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/9192821396136462852'/><link rel='alternate' type='text/html' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html?showComment=1260589350658#c9192821396136462852' title=''/><author><name>Anonymous</name><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html' ref='tag:blogger.com,1999:blog-2987032012497124857.post-5581690029207099111' source='http://www.blogger.com/feeds/2987032012497124857/posts/default/5581690029207099111' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-2987032012497124857.post-9057273692628586653</id><published>2009-11-20T09:33:48.463-08:00</published><updated>2009-11-20T09:33:48.463-08:00</updated><title type='text'>Anonymous, how is the net.tcp binding configured o...</title><content type='html'>Anonymous, how is the net.tcp binding configured on the service? In particular, is security turned off? The binding should look similar to this:&lt;br /&gt;&lt;br /&gt;&amp;lt;netTcpBinding&amp;gt;&lt;br /&gt;  &amp;lt;binding name=&amp;quot;PubSub&amp;quot;&amp;gt; &lt;br /&gt;    &amp;lt;security mode=&amp;quot;None&amp;quot;/&amp;gt; &lt;br /&gt;  &amp;lt;/binding&amp;gt; &lt;br /&gt;&amp;lt;/netTcpBinding&amp;gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/9057273692628586653'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/9057273692628586653'/><link rel='alternate' type='text/html' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html?showComment=1258738428463#c9057273692628586653' title=''/><author><name>Tomasz Janczuk</name><uri>http://www.blogger.com/profile/14273379892104866795</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='08472674204894008885'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html' ref='tag:blogger.com,1999:blog-2987032012497124857.post-5581690029207099111' source='http://www.blogger.com/feeds/2987032012497124857/posts/default/5581690029207099111' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-2987032012497124857.post-5096962919059727176</id><published>2009-11-20T04:56:16.282-08:00</published><updated>2009-11-20T04:56:16.282-08:00</updated><title type='text'>Hi

The Visual Studio 2010 integration is failing....</title><content type='html'>Hi&lt;br /&gt;&lt;br /&gt;The Visual Studio 2010 integration is failing. When I try to reference a tcp service in a SL 4.0 application, a message saying that there is no endpoints compatible with SL 3.&lt;br /&gt;&lt;br /&gt;I uninstalled the SL 3 SDK before install 4.0, and the problem continues happening.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/5096962919059727176'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/5096962919059727176'/><link rel='alternate' type='text/html' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html?showComment=1258721776282#c5096962919059727176' title=''/><author><name>Anonymous</name><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html' ref='tag:blogger.com,1999:blog-2987032012497124857.post-5581690029207099111' source='http://www.blogger.com/feeds/2987032012497124857/posts/default/5581690029207099111' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-2987032012497124857.post-6863654136655787893</id><published>2009-11-19T12:05:53.217-08:00</published><updated>2009-11-19T12:05:53.217-08:00</updated><title type='text'>We realize lack of transport level security is a m...</title><content type='html'>We realize lack of transport level security is a major drawback in the current implementation of net.tcp and we consider this an important feature to add going forward. &lt;br /&gt;&lt;br /&gt;Silverlight does not currently support message protection (integrity and confidentiality) using WS-Security mechanisms. The only WS-Security feature supported by WCF in Silverlight is attaching basic username/password credentials to a message. However, such configuration requires transport level security. Given that net.tcp does not provide transport level security, basic credentials in WCF can only be added to messages sent over the HTTPS protocol. &lt;br /&gt;&lt;br /&gt;There is no single &amp;quot;proper&amp;quot; duplex communication channel in Silverlight, the choice depends on the requirements. Net.tcp offers performance far superior to HTTP polling duplex; at the same time its practical use is restricted to intranets due to TCP port range limitation and lack of transport level security. Going forward we plan to invest in adding SSL security to net.tcp as well as improving HTTP polling duplex performance. &lt;br /&gt;&lt;br /&gt;The System.ServiceModel.Extensions.dll and System.ServiceModel.NetTcp.dll are Silverlight extension assemblies and ship as part of Silverlight 4 SDK. They are typically located in &amp;quot;%Program Files%\Microsoft SDKs\Silverlight\v4.0\Libraries\Client&amp;quot; directory.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/6863654136655787893'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/6863654136655787893'/><link rel='alternate' type='text/html' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html?showComment=1258661153217#c6863654136655787893' title=''/><author><name>Tomasz Janczuk</name><uri>http://www.blogger.com/profile/14273379892104866795</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='08472674204894008885'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html' ref='tag:blogger.com,1999:blog-2987032012497124857.post-5581690029207099111' source='http://www.blogger.com/feeds/2987032012497124857/posts/default/5581690029207099111' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-2987032012497124857.post-6374471418729467513</id><published>2009-11-19T05:33:26.572-08:00</published><updated>2009-11-19T05:33:26.572-08:00</updated><title type='text'>Where are these assemblies?</title><content type='html'>Where are these assemblies?</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/6374471418729467513'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/6374471418729467513'/><link rel='alternate' type='text/html' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html?showComment=1258637606572#c6374471418729467513' title=''/><author><name>Anonymous</name><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html' ref='tag:blogger.com,1999:blog-2987032012497124857.post-5581690029207099111' source='http://www.blogger.com/feeds/2987032012497124857/posts/default/5581690029207099111' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-2987032012497124857.post-1553963214505238986</id><published>2009-11-19T03:51:39.005-08:00</published><updated>2009-11-19T03:51:39.005-08:00</updated><title type='text'>So is this a "proper" duplex communication channel...</title><content type='html'>So is this a &amp;quot;proper&amp;quot; duplex communication channel as opposed to polling duplex?</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/1553963214505238986'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/1553963214505238986'/><link rel='alternate' type='text/html' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html?showComment=1258631499005#c1553963214505238986' title=''/><author><name>Anonymous</name><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html' ref='tag:blogger.com,1999:blog-2987032012497124857.post-5581690029207099111' source='http://www.blogger.com/feeds/2987032012497124857/posts/default/5581690029207099111' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-2987032012497124857.post-817495815964081862</id><published>2009-11-18T18:16:35.384-08:00</published><updated>2009-11-18T18:16:35.384-08:00</updated><title type='text'>Is message-level security supported even though tr...</title><content type='html'>Is message-level security supported even though transport-level isn&amp;#39;t?</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/817495815964081862'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/817495815964081862'/><link rel='alternate' type='text/html' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html?showComment=1258596995384#c817495815964081862' title=''/><author><name>Anonymous</name><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html' ref='tag:blogger.com,1999:blog-2987032012497124857.post-5581690029207099111' source='http://www.blogger.com/feeds/2987032012497124857/posts/default/5581690029207099111' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-2987032012497124857.post-4390386704853022810</id><published>2009-11-18T13:49:53.756-08:00</published><updated>2009-11-18T13:49:53.756-08:00</updated><title type='text'>shame about the lack of security</title><content type='html'>shame about the lack of security</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/4390386704853022810'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/4390386704853022810'/><link rel='alternate' type='text/html' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html?showComment=1258580993756#c4390386704853022810' title=''/><author><name>Anonymous</name><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html' ref='tag:blogger.com,1999:blog-2987032012497124857.post-5581690029207099111' source='http://www.blogger.com/feeds/2987032012497124857/posts/default/5581690029207099111' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-2987032012497124857.post-6590605284103885272</id><published>2009-11-18T12:34:14.138-08:00</published><updated>2009-11-18T12:34:14.138-08:00</updated><title type='text'>Wow, interesting data. Do you have numbers for a O...</title><content type='html'>Wow, interesting data. Do you have numbers for a OSX-based client?</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/6590605284103885272'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2987032012497124857/5581690029207099111/comments/default/6590605284103885272'/><link rel='alternate' type='text/html' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html?showComment=1258576454138#c6590605284103885272' title=''/><author><name>alexdej</name><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html' ref='tag:blogger.com,1999:blog-2987032012497124857.post-5581690029207099111' source='http://www.blogger.com/feeds/2987032012497124857/posts/default/5581690029207099111' type='text/html'/></entry></feed>