Rewording of "redundant binary objects" use case

• From: Herve Ruellan <herve.ruellan@crf.canon.fr>
• Date: Fri, 17 Oct 2003 17:09:39 +0200
• To: xml-dist-app@w3.org
• Message-ID: <3F900633.2020504@crf.canon.fr>

As per my Action Item from 2003/10/15 telcon, here is a rewording of the 
streaming use case with redundant binary objects.

<UseCase>
An application wishes to send a SOAP message that contains one or more 
redundant binary pieces of data. Each redundant binary piece of data is 
actually contained in several locations of the SOAP message (for 
example, the SOAP message could contains an SVG document describing a 
multipage document, each page of the document containing the PNG logo of 
the company which authored the document). For design reasons, this data 
cannot be referenced externally, but must be transported with the 
message. Doing so by replicating each redundant binary piece of data as 
many times as it is contained in the SOAP message involves an 
unacceptable message size, due to bandwidth, latency and/or storage 
requirements.
</UseCase>

Regards,

Hervé.

Received on Friday, 17 October 2003 11:16:12 UTC