It’s just data
The sweet spot is GET and POST of XML Infomation Sets. REST's content independence and SOAP's transport independence are simultaneously both key strengths and weaknesses of each approach. Both contain speculative features that have not been widely adopted (e.g., DELETE? Content-Negotiation?). The most underrated feature of SOAP is asynchronous messaging.
REST + SOAP is a powerful combination.
REST vs SOAP...
[more]
Trackback from Sam Gentile's Blog
At the risk of replaying the Spanish Inquisition Sketch - The most underrated feature is the ability to do async. messaging and the namespaced headers that will allow some degree of interop amongst all the ws-**** out there.
j
Sam Ruby: REST vs SOAP: "REST + SOAP is a powerful combination." And let's not forget that REST is nothing more than an architectural pattern. A vast unexplored area is...
[more]
Trackback from snellspace
John McDowall says: async. messaging. XMPP (Jabber) is a pretty good way to send chunks of XML around the network asynchronously, securely, and with low latency.
Posted by Joe Hildebrand atSam Ruby offers some feedback on a recent SOAP vs. REST article. I have to weigh in a bit here, having just finished a wholehearted attempt to build a RESTful SOAP implementation. Did I come close? The 'O' in SOAP is a misnomer. We...
Excerpt from John Burkhardt atDon Box responded to my constant non-proliferation of standards ramble. This is the power of blogs. Blog it and great guys like Don will respond. Now, it's time for my rebuttal. I challenge the said great men to put actions where their words lie. I...
Excerpt from iBLOGthere4iM atDon Box responded to my constant non-proliferation of standards ramble. This is the power of blogs. Blog it and great guys like Don will respond. Now, it's time for my rebuttal. I challenge the said great men to put actions where their words lie. I...
Excerpt from iBLOGthere4iM at