XML over HTTP or SOAP?
While keeping tabs on the J2EE/.NET debate with a recent discussion by 'Programming Legends' here:
I found this post in the discussion thread of interest and thought I'd link to it here:
XML-over-http is the way
This is like the Nth time I'll make the same point, but since there was so much SOAP chatter on this thread I couldn't resist. Here goes:
SOAP is to XML what EJB is to Java. A heavy handed, over applied behemoth. SOAP is usurping the "web service" definition. SOAP is supposed to make systems interoperable, but in *every* deployment, or contemplated deployment I have seen, where interoperability was crucial, SOAP had the effect of reducing interoperability.
I'm right now seeing an organization (won't say which) on the verge of making a fateful commitment to SOAP, even though its own internal experiments showed that SOAP actually reduced the interoperability in contrast to XML-over-http.
A blind reliance on tools (Axis and .Net) combined with relentless "web service" marketing spin has the entire organization hypnotized.
In contrast, a simple, well-crafted XML schema combined with HTTP is the paragon of simplicity and interoperability. A custom XML schema can produce document instances with very high signal-to-noise ratios, but also excellent human readability.
SOAP is a red herring. XML schema + binding tools is the path of the righteous.