Comments on: SOAP vs. REST API Implementation

By: web site hosting

web site hosting — Tue, 10 Jan 2012 17:32:20 +0000

Above the topic are explained very clearly Mind.Every one like this kind of valuable information.

By: Hobby ID Action Figure Catalog

Hobby ID Action Figure Catalog — Tue, 09 Aug 2011 06:54:52 +0000

Im developing an API for my site HobbyID.com. In doing research I've considered using SOAP or REST however Im concerned that some site which connect to the API may not have the PHP libs installed for these, and may not have adin rights to get them installed. So I'm considering using old fashion get_file_contents (dont wanna use curl as that may not be installed either) to call my host which will process and return XML content. Does anyone agree/dissagree with this decision?

By: hire a web programmer

hire a web programmer — Tue, 02 Aug 2011 11:19:33 +0000

I was looking for this information. Just so you know I discovered your web site when I was searching for blogs like mine, so please check out my site sometime and leave me a comment to let me know what you think.
hire a website developer | hire web developers

By: Website Designer Riyadh

Website Designer Riyadh — Thu, 28 Jul 2011 12:57:31 +0000

I like this post. I want to more detail about this topic and now, I got all information by your post. Everything define in this post is amazing. I think you should make more post which helps us.
Web Designer Riyadh | Riyadh website design company

By: Xvxcvxcvcxv

Xvxcvxcvcxv — Mon, 25 Jul 2011 10:33:30 +0000

By: NT

NT — Wed, 02 Mar 2011 21:00:12 +0000

After reading this and other articles on the SOAP v REST debate I'm going to opt for REST for my web services especially as the requests and subsequent responses will be fairly simple. REST seems to make the client side much easier which can only be a good thing.

By: Introduction to writing a REST server in PHP | Fliquid Studios

Introduction to writing a REST server in PHP | Fliquid Studios — Tue, 13 Jan 2009 04:16:09 +0000

[...] article is the second in my SOAP and REST API series, following on from my SOAP vs. REST API Implementation article and will fill in some more of the details around implementing a REST server in [...]

By: SOAP vs REST — a common misconception? - biotext.org.uk

SOAP vs REST — a common misconception? - biotext.org.uk — Sat, 03 Jan 2009 14:34:22 +0000

[...] Andrew on Jan.03, 2009, under Rants Michael Little at Fliquid Studios recently posted an interesting comparison of SOAP vs REST which may have accidentally perpetuated a misconception about SOAP that I believe is fairly common. [...]

By: Andrew Clegg

Andrew Clegg — Sat, 03 Jan 2009 14:01:28 +0000

Sure, sorry, I didn’t mean to suggest that this was actually a non-issue with SoapServer. I have no experience with that particular toolkit so it might be a serious problem. At the same time, however, it might be worth digging into its internals to find a way to extract the XML directly, which would give it the exact same universal compatibility that REST enjoys.

Having looked at various SOAP toolkits in the Java world, and C#.NET’s implementation in a previous life, I’d say that this is an important capability to look for when choosing a web services stack (where the stack might well include the choice of language as well as toolkit).

By: Michael Little

Michael Little — Mon, 29 Dec 2008 00:13:24 +0000

Hi Andrew,

Firstly, thanks for taking the time to leave such an extensive comment. It is greatly appreciated.

Your comment about the overhead of SOAP ties in exactly with what I was saying about the complexity of the request. If the request is complex (and no doubt large) you will no doubt be better off using SOAP and the overhead will indeed be a negligible amount.

In regards to your comment: “This is a much more serious misconception as it confuses the messaging protocol (SOAP) with the databinding layer” – I’m not sure I agree with this. While what you are saying is correct, this article is intended to be related to the practical implementation of SOAP/REST in PHP. In PHP this is a definite problem with the SoapServer class and no doubt many other SOAP toolkits have similar problem or incompatibilities. Whether it is an issue with the SOAP specification or not (I am not suggesting it is) is irrelevant.