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

Re: Rewording of "redundant binary objects" use case

From: Robin Berjon <robin.berjon@expway.fr>
Date: Fri, 17 Oct 2003 17:21:44 +0200
Message-ID: <3F900908.9040604@expway.fr>
To: Herve Ruellan <herve.ruellan@crf.canon.fr>
Cc: xml-dist-app@w3.org

Herve Ruellan wrote:
> 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>

I agree with the use case being interesting in general, but I'd like to point 
out that your example with SVG is unrealistic. SVG has ways to reference content 
so that it would be a be silly (and in truth unlikely) that one will ever author 
a document in which you would copy an image several times: you put it in a 
<defs> section, and reference it.

-- 
Robin Berjon <robin.berjon@expway.fr>
Research Scientist, Expway      http://expway.com/
7FC0 6F5F D864 EFB8 08CE  8E74 58E6 D5DB 4889 2488
Received on Friday, 17 October 2003 11:23:48 GMT

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