W3C home > Mailing lists > Public > xml-dist-app@w3.org > June 2004

Re: Features: required implementation and use (was Re: Describing which blobs are to be optimized.)

From: Jean-Jacques Moreau <jean-jacques.moreau@crf.canon.fr>
Date: Thu, 10 Jun 2004 10:02:28 +0200
Message-ID: <40C81594.7060906@crf.canon.fr>
To: Hugo Haas <hugo@w3.org>
Cc: Glen Daniels <gdaniels@sonicsoftware.com>, Marc Hadley <Marc.Hadley@Sun.COM>, www-ws-desc@w3.org, xml-dist-app@w3.org

This of course extends to other nodes on the message path 
(intermediaries) or other nodes involved in the pattern/mep (multicast, 
3-node interaction, etc.).

JJ.

Hugo Haas wrote:

>* Glen Daniels <gdaniels@sonicsoftware.com> [2004-06-07 11:49-0400]
>[..]
>  
>
>>Second, we could add something like a "mustUnderstand" attribute to
>>feature/module declarations, which indicates that anyone using the WSDL
>>must understand the given extension, but that the usage of that
>>extension is still optional unless "required='true'" is specified.
>>Required extensions would remain as they are - where both usage and
>>understanding are mandated.  This would allow specifying features which
>>may or may not be used, but whose use affects the syntax/semantics of
>>the exchange enough that failure to understand them would completely
>>screw things up in the event they were used.
>>    
>>
>
>It raises interesting questions when considering MTOM.
>
>When the HTTP Transmission Optimization Feature is in use, the media
>type of the entity received changes from application/soap+xml to
>mime/multipart-related, which means that an agent not supporting the
>feature is going to be seriously confused, and return a 415 according
>to the SOAP HTTP binding[1] if it's the provider agent, or probably
>just discard the message it's the requester agent.
>
Received on Thursday, 10 June 2004 04:03:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:18 GMT