Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I think that you will find that PHP developers are more likely to prefer RESTful interfaces. Here is a 2003 article about it.</p> <p><a href="http://onlamp.com/pub/a/php/2003/10/30/amazon_rest.html" rel="nofollow noreferrer">http://onlamp.com/pub/a/php/2003/10/30/amazon_rest.html</a></p> <p>RESTful interfaces are a growing phenomenon and if you need to attract developers to your platform it will be easier if you catch the wave.</p> <p>Having said that, is there a good reason why you cannot support multiple interfaces? This is fairly common in web services that do not have a captive audience. You could support your legacy model, a clean RESTful model and a SOAP/WSDL model. Then take stock after 6 months to a year to see which model is the most popular and least effort to support.</p> <p>When it comes to making the site more accessible to outsiders, REST has more widespread usage. As far as saving your project, it is possible that SOAP would do this because it demands a certain amount of rigor in interface design, however the same could be said of REST. If this is a key criterion, then you should probably abandon the hand-coded XML and go with a high-level interface design that could be implemented as both REST and SOAP.</p> <p>I know some people believe that SOAP and REST are fundamentally different approaches, but if you take a RESTful approach to the interface design, you shouldn't have great difficulty in creating a SOAP version. Don't try to do it the other way around though.</p>
 

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