Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The best approach you can go with is exposing a <strong>RESTful WCF</strong> service using the WebHttpBinding which is designed for interoperable xml, json conversations. Then any client could issue an HTTP request to the endpoint and get the plain REST result. One downside of this technique is that you'll have to get familiar with WCF RESTful programming model which is described here <a href="http://msdn.microsoft.com/en-us/magazine/dd315413.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/magazine/dd315413.aspx</a> And you can find a comprehensive discussion on this topic here <a href="http://social.msdn.microsoft.com/Forums/en-US/wcf/thread/90716451-fd29-4917-a5ca-f7f3bcaa96c9" rel="nofollow noreferrer">http://social.msdn.microsoft.com/Forums/en-US/wcf/thread/90716451-fd29-4917-a5ca-f7f3bcaa96c9</a></p> <p>The second approach, that you'll probably like more because of its simplicity is using BasicHttpBinding service accessed through the <strong>PHP buil-in SoapClient</strong>. There's a good source illustrating .Net data type transmission to the PHP client. So you can use the same approach with your data: <a href="https://stackoverflow.com/questions/8763980/passing-array-of-objects-from-wcf-to-php-extracting-the-info">Passing array of objects from WCF to PHP - extracting the info</a> Just be careful and properly design your data contract class with [DataContract]/[DataMember] attributes.</p> <p>And the following is for PHP WCF/BasicHttpIntegration starters: <a href="http://cgeers.com/2009/08/20/using-wcf-services-with-php-5/" rel="nofollow noreferrer">http://cgeers.com/2009/08/20/using-wcf-services-with-php-5/</a></p> <p><strong>REST vs SOAP</strong> It's not that true that REST limits the WCF power, it actually does for some advanced WCF features mostly because of WebHttpBinding's limitations. But REST, in turn, is much more interoperable than any RPC protocols, like SOAP is. Plus you get lightweight JSON support in that case. So your decision depends on your needs and your system's overall requirements/architecture. Agree, that if you just need to deliver a data-set like object to a few clients (especially if it's a local system, not published over internet) then, for the sake of simplicity, BasicHttpBinding/SOAP is the best for you.</p> <p>One more thing to mention, that a lot of web services are either RESTful or being converted to REST. So does Microsoft too. It's the best way to deliver the data to the client's browser directly (JS takes the handle).</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload