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

Re: Requirements for attachments^H^H^H transport optimisation

From: Patrick Steer <webmaster@die-werbung.de>
Date: Sat, 3 Jul 2004 10:46:31 -0400 (EDT)
Message-ID: <40E6C6C1.8000706@die-werbung.de>
To: xml-dist-app@w3.org

I think it would be useful to spend a little time identifying the 
higher-level requirements surrounding MTOM and the like. These are the 
ones I'm aware of: 1) Reduce "bytes on the wire", to improve bandwidth 
usage / transport latency. 2) Reduce processing overhead during the 
generation and consumption of messages. 3)
Enable selective reordering in the serialization of message components, 
to allow flexibility in processing. The third deserves a bit more 
explanation; a use case might be placing a large binary file after the 
SOAP envelope in the serialized message, so that an intermediary (or 
ultimate receiver, for that matter) can act upon the message before 
reading all of the bytes off the wire.

Are there any other high-level requirements associated with the abstract 
MTOM feature? I think it would be nice to call these out in the document 
at some point. It would also be good to note that these can all be seen 
as encoding issues and nothing more.
Received on Monday, 5 July 2004 15:23:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:26 UTC