On 1/20/14 9:42 AM, Koester, Michael wrote:
Given that this would not be for "public consumption" (i.e., only
targeted at the web site developed for the business) would that be a
problem? The web developer and I would agree on the spec, and it
would only change for a mutually agreed upon design change.

Well, that depends on whether you need to actively keep it private, but generally speaking, if you're not going to publish the web service, then there's even less reason to prefer SOAP over REST: SOAP's biggest strength is that it's highly standardized, and its biggest weakness is that if you have to parse or construct it yourself, without benefit of canned tools, it's a pain in the butt to deal with.

(That's not to say that some RESTful web services aren't also a pain in various portions of the anatomy, if you have to build your own tools to access them, but if you're in control of both sides of the conversation, REST gives you the freedom to design it strictly to fit your own needs, without having to bother with complex XML message structures.)

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].