- From: Glen Daniels <gdaniels@sonicsoftware.com>
- Date: Tue, 1 Jun 2004 22:56:40 -0400
- To: "Prasad Yendluri" <pyendluri@webmethods.com>
- Cc: <www-ws-desc@w3.org>
Hi Prasad: > ><feature > uri="http://www.w3.org/2003/06/soap/features/http-optimization > " <http://www.w3.org/2003/06/soap/features/http-optimization> > > required="true"/> > >If your underlying protocol binding > >did not support this feature, you'd get a fault. Otherwise, > you'd get > >MTOM/XOP serialized messages. > > The HTTP Transmission Optimization Feature [1] fixes the > transport to HTTP in addition to XOP serialization. > > The text above seems to imply the this can be used with > "other" protocol bindings for SOAP as well. > Are we adding in that flexibility at the WSDL 2.0 level? The intent is simply to support this in the standard SOAP HTTP binding, but we could certainly imagine alternate SOAP/HTTP bindings which might support it as well. You're quite right though, it would only make sense to specify this for a binding which actually supported the feature in question - non-HTTP bindings couldn't well do that in this case (though they certainly could support the abstract optimization feature, or other less-http-specific features that used XOP and MIME). --Glen
Received on Tuesday, 1 June 2004 22:56:47 UTC