Lists Home |
Date Index |
firstname.lastname@example.org (Don Box) writes:
>Most of the SOAP spec is dedicated to the processing model of the
>"mashed header/body" of a SOAP envelope. Check out part 1 of the
>current SOAP/1.2 spec for more details.
I'm aware of what SOAP does. I just think it's a bad idea.
>FWIW, SOAP headers were introduced back in the 1990's to allow for
>orthogonal extensibility over app-specific payloads. As for SOAP vs.
>MIME vs. HTTP headers, SOAP tries to generalize the concept of an
>intermediary to allow more flexibility in forming a message path. I
>believe this is a non-goal for MIME and rather is left for HTTP, SMTP,
>etc. to invent for themselves.
I think SOAP has made a gigantic mistake in this regard, and its
insistence on an envelope has created new problems for XML like the
recurring need to subset XML that pops up on TAG. ("You can't stuff a
whole XML document with DOCTYPE into this 'envelope' we created, so
let's chop up the contents into bits we can digest.")
Developing a protocol that used XML for headers might well have made
sense. Developing a protocol that slaps headers and content into a
single XML document as children of an envelope is very different.
It's especially unfortunate given that HTTP already had a history of
using (MIME-based) headers for message path management, and SOAP still
most frequently rides inside of that.
Not like I can stop it of course, but marveling at SOAP's ghastliness is
an entertaining sport, one that seems unlikely to disappear.
Ring around the content, a pocket full of brackets
Errors, errors, all fall down!
http://simonstl.com -- http://monasticxml.org