Have Geek Brain

Silverlight + smart client operations in one service?

For my project web services, I want to support desktop and silverlight clients. Should I write a separate web service for each, or do all the operations in one service? If I put them all in one, I have to go with basicHttpBinding. Now the winforms app is using wsHttpBinding, what am I missing with basicHttpBinding?

0


a source to share


2 answers


I highly recommend that you read this carefully:

Comparing Silverlight and WCF

http://msdn.microsoft.com/en-us/library/cc896571(VS.95).aspx



There are many challenges when developing a web service for use in Silverlight, especially if you already have a wsHttpBinding solution. Good luck!

EDIT: Also I found this article helpful:

WCF: BasicHttpBinding versus WSHttpBinding at the SOAP package level http://geekswithblogs.net/claeyskurt/archive/2008/04/22/121508.aspx

+2


a source


Use one web service with two endpoints, allowing you to support basicHttpBinding as well as wsHttpBinding.



The difference between the two bindings is that basic is Soap 1.1 whereas ws is Soap 1.2 and WS-Addressing specs, besides, wsHttpBinding offers more security options

+1


a source






More articles:


All Articles