Hi y'all:
In fulfillment of my action item from the F2F, the following snippet in
our current syntax seems to be all you would need to ensure that the
HTTP Transmission Optimization Feature described in [1] is utilized:
<feature uri="http://www.w3.org/2003/06/soap/features/http-optimization"
required="true"/>
This would go in your SOAP binding. If your underlying protocol binding
did not support this feature, you'd get a fault. Otherwise, you'd get
MTOM/XOP serialized messages.
Specifying the feature with required="false" would indicate to a user
that MTOM/XOP serialization is supported by the service, but not
required.
--Glen
[1]
http://www.w3.org/2000/xp/Group/3/06/Attachments/OptimizationMechanism.h
tml#xop-serialization