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

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 <[email protected]> [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.
>