Two more articles hit my inbox today. Both asking that we stop the silly emacs vs vi SOAP vs REST debate.
Could we? Thanks.
I’m hoping by 2007 we’ll stop arguing abstractions and learn to accept the differences and diversity of options. Two technologies, each suited to solve a different set of problems. Choice. Now what could be wrong with choice?
But I can’t bear reading another article where XML/HTTP gets confused with REST. Can we stop with that? Bloggers can also fact check. Use Wikipedia. It’s free.
SOAP is mostly enveloping around XML/HTTP. The devil is in that “all you can stuff” envelope. Unassuming, but it can hide an army of 3-ring binders and message handler chains. Still, it’s mostly about that envelope.
Which is why I accept the argument that XML/HTTP is “SOAP Lite”. Some say that to belittle SOAP, some because they know simpler is better. Either way, we’re arguing color and taste of apples, which is a good thing. BTW, I like mine pesticide free.
But REST is not XML/HTTP and never was.
Just because you change encoding to remove the envelope, allow request even if they’re not POST, and parse operation name from URL, doesn’t mean you’re doing REST. You’re not even faking it. It’s still WS-* with a different on-wire format.
The argument that Axis2 and Indigo do REST is nonsense. They don’t. They do SOAP lite.
Do you really believe that SOAP and REST are two of the same and we’re just debating implementation details? Are you willing to stand behind those words?
Show me.
Switch your blog from REST to SOAP.
Oh, and since I won’t have access to your feed anymore, can you please e-mail me your WSDL. I might have some spare time to create a SOAP client, so I can POST retrieve future entries, since your blog is no longer on the Interweb.
That way I know you’re still blogging with conviction. And I can admit I’m wrong.
It’s all just implementation details.
Image by ohsleepless1
Trying to clean it up and put it to bed… — Chip’s Quips