Issue 154: use of XOP with HTTP binding

As per my action item from yesterday's call, I had a look into
serializing messages as multipart/related with the HTTP binding.

I originally indicated on the call that we can support MIME multipart
in the HTTP binding by simply using the HTTP Transmission Optimization
Feature[5], just leaving us with the problem of indicating which
element nodes to serialize externally with XOP.

I have now realized that this particular feature requires the use of a
SOAP body, so this will only work for SOAP. Basically, if we wanted to
use XOP for the HTTP binding, we would need to describe how to use XOP
in the context of the HTTP binding, which would basically be the XML
over HTTP Transmission Optimization Mechanism, which is out of scope
IMO, so I would lean towards closing this issue with no action.

In any case, if somebody was defining the XML over HTTP Transmission
Optimization Mechanism based on XOP, then I think it would just work
by indication in the WSDL document that this feature is in use. So our
design doesn't preclude a multipart/related serialization.

Regards,

Hugo

  5. http://www.w3.org/TR/2004/WD-soap12-mtom-20040209/#HTTP-implementation
-- 
Hugo Haas - W3C
mailto:hugo@w3.org - http://www.w3.org/People/Hugo/