W3C home > Mailing lists > Public > xml-dist-app@w3.org > September 2003

use cases for MTOM

From: Mark Nottingham <mark.nottingham@bea.com>
Date: Tue, 2 Sep 2003 14:43:49 -0700
To: "Xml-Dist-App@W3. Org" <xml-dist-app@w3.org>
Message-Id: <896355A7-DD8E-11D7-8446-00039396E15A@bea.com>

I had an AI to generate some text for MTOM use cases. This is a 
starting point;


* Undesirable Message Bloat
An application wishes to send a SOAP message that contains a large 
binary piece of data; e.g., a JPG image, binary executable or other 
sizeable, non-textual data. For design reasons, this data cannot be 
referenced externally, but must be transported with the message. Doing 
so using base64Binary or similar encoding involves an unacceptable 
message size, due to bandwidth, latency and/or storage requirements.

* Undesirable Processing Overhead
An application wishes to send a SOAP message that contains a large 
binary piece of data; e.g., a JPG image, binary executable or other 
sizeable, non-textual data. For design reasons, this data cannot be 
referenced externally, but must be transported with the message. Doing 
so using base64Binary or similar encoding involves unacceptable message 
generation and/or parsing overhead, due to throughput requirements, 
device limitations and/or other considerations.

* Focused Intermediaries
An intermediary wishes to process a large message, but only needs to 
access a small section of the message. For efficient operation, it 
needs to be able to construct the relevant parts of the message infoset 
without actually reading and parsing the rest of the message, whilst 
still being able to successfully forward the entire message.


--
Mark Nottingham   Principal Technologist
Office of the CTO   BEA Systems
Received on Tuesday, 2 September 2003 17:44:05 GMT

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