Have Geek Brain

Why only basicHttpBinding with silverlight and wcf?

Duplicate: Why does Silverlight 2 only support WCF basicHTTP binding?

Why only basicHttpBinding with silverlight and wcf? Maybe you have a link that covers this, you don't have to do a bunch of typing: +>

+1


a source to share


3 answers


Multiple Answers: (1) Silverlight 4 now makes the Net.TCP binding available, which is pretty damn handy when it's not blocking as it is significantly faster (see here ). It is so clear that there is nothing in the Silverlight architecture that prevents it from using other bindings.

(2) As to why Silverlight doesn't use other WS * Http bindings, that's just a guess, but I wouldn't be surprised if those bindings use HTTP in such a way that Silverlight's limited HTTP stack won't be supported, perhaps for security reasons ... For example, I know that Silverlight limits the content headers that you can put in an HTTP request, and if any of the WS- * returns require custom headers or headers that could pose a security risk, MS would like to prevent this.



(3) Of course, it's possible that MS hasn't gotten to him yet. They've done a lot with Silverlight over the past couple of years, but apparently they should prioritize their functionality.

+1


a source


Hmm, I'm sure it's a duplicate, but can't find it. I think the short answer is that BasicHttpBinding is the only binding that works in Partial Trust.



(EDIT: Found a duplicate linked in the question now)

0


a source


I found several links for this but did not provide a definitive answer. Smells like Silverlight were developed against ASMX web services for Web services style communication and a way to make WCF play with legacy clients, expecting the ASMX web service to use the basicHttp binding.

This link gives you a fully rendered example (using Silverlight beta).
http://msdn.microsoft.com/en-us/magazine/cc794260.aspx

A standard WCF service can be called by a Silverlight application if the Silverlight application has a binding of type basicHttpBinding. You should either make sure you change the default binding of the WCF service from wsHttpBinding to basicHttpBinding or create a new binding of type basicHttpBinding

This guide says the same thing, but again there is no explanation. http://timheuer.com/blog/archive/2008/03/14/calling-web-services-with-silverlight-2.aspx

Silverlight binds using BasicHttpBinding for WCF

0


a source






More articles:


All Articles