Simon Fell > Its just code

Thursday, May 02, 2002

Keith Replies ... However, I don't think I'm understood. I don't mean, "how do I tell that a piece of XML is a SOAP message", but given any SOAP message, how I tell the "type" of that SOAP message? Sounds a lot like Tim & Martin's point that there's no common way to reffer to a binding/operation outside of WSDL [I guess some XPath type approach that works on the logical WSDL model is the closest you can get today]. I'm sure this'll be fixed in WSDL 1.2, right Keith ? But, if you're taking a messaging approach, then all you really care about is the schema right ?, for which you should be able to extract based on the QNames used in the message.
< 8:00:15 PM # more elsewhere > Chilled Euphoria - Digitally Mixed By Red Jerry - CD 1 (Tag's Trance Trip - A Progressive Journey into Next Generation Radio)

My proposal doesn't modify HTTP at all.... [Snell's Blog] There isn't a single HTTP stack out there that will know what to do with INVOKE. This negates 99% of the reasons to use HTTP.
< 7:28:45 PM # more elsewhere > Toby Doran - Unearthed (Tag's Trance Trip - A Progressive Journey into Next Generation Radio)

....Given any XML document, you can look at it's default namespace and tell it's type. [KeithBa's Blog] I'm going to assume that this is a typo, if not, Keith should know better. The default namespace MEANS NOTHING! Its perfectly valid for a WSDL doc to not have the WSDL namespace as its default namespace (as long as the elements are qualified properly). The root element QName (the element local name + namespace URI) tells you that a WSDL doc is a WSDL doc, why is SOAP any different ?, the root element QName ( {http://schemas.xmlsoap.org/soap/envelope/}Envelope for SOAP 1.1 ) tells you that its a SOAP message.
< 6:03:19 PM # more elsewhere > `White Label` Euphoria CD2, Mixed by John `00` Flemming (Tag's Trance Trip - A Progressive Journey into Next Generation Radio)

I've organized some thoughts on the use of HTTP POST and GET with SOAP. After going back to the HTTP specification, I came up with a somewhat surprising (to me) conclusion: for SOAP RPC, what we need is a new HTTP Operation called INVOKE. Read this for details.

Bottom line: SOAP RPC SHOULD NOT USE HTTP POST.[Snell's Blog] If its going to take modifying HTTP to use it with SOAP, then it seems completely pointless to use HTTP at all, its hardly an ideal transport for SOAP to begin with.
< 5:56:07 PM # more elsewhere > `White Label` Euphoria CD2, Mixed by John `00` Flemming (Tag's Trance Trip - A Progressive Journey into Next Generation Radio)