Re: Expressing MTOM/XOP using feature syntax

Hi Glen,

>HTTP Transmission Optimization Feature described in [1] is utilized:
>
><feature uri="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? 


[1] 
http://www.w3.org/2000/xp/Group/3/06/Attachments/OptimizationMechanism.html#HTTP-implementation

Regards, Prasad

-------- Original Message --------
Subject: 	Expressing MTOM/XOP using feature syntax
Resent-Date: 	Tue, 25 May 2004 08:31:22 -0400 (EDT)
Resent-From: 	www-ws-desc@w3.org
Date: 	Tue, 25 May 2004 08:31:22 -0400
From: 	Glen Daniels <gdaniels@sonicsoftware.com>
To: 	<www-ws-desc@w3.org>


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.html#xop-serialization