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

Re: Re: new version of requirements following ARTF telcon of 2003-01-15

From: John J. Barton <John_Barton@hpl.hp.com>
Date: Tue, 21 Jan 2003 09:57:24 -0800
Message-Id: <5.1.1.6.2.20030121094357.028093b0@hplex1.hpl.hp.com>
To: jones@research.att.com, chrisfer@us.ibm.com
Cc: xml-dist-app@w3.org

At 10:03 PM 1/20/2003 -0500, Mark Jones wrote:
> >
> > DR13. The specification must provide support for large parts.
>
>And small ones as well one would imagine. How large? Arbitrarily
>large? Just "pretty big", really, really large" or "incomprehensibly
>large"? :)
>
>What about parts who's size is not known at the time that
>the serialization is begun?
>
><mark>These points have been discussed briefly.  This one needs more
>work. </mark>

The reason for this kind of requirement is the dominant impact of I/O
and memory allocation on performance.  For small messages, all
attachment scheme will be equal since CPUs are infinitely fast.
"Large" of course changes over time as hardware resources improve.
Design for messages between 1MB and 1GB.  5 years from now, when
this standard is in use, allocators can bite off 1MB but 1GB will likely
still call for disk.  You can shift these numbers around, but they will
factor into the design: might as well discuss them explicitly.

In my opinion, parts whose size is not known should not be "attached"
to SOAP messages.  Rather one should use messages to set up an
out of band stream mechanism.

______________________________________________________
John J. Barton          email:  John_Barton@hpl.hp.com
http://www.hpl.hp.com/personal/John_Barton/index.htm
MS 1U-17  Hewlett-Packard Labs
1501 Page Mill Road              phone: (650)-236-2888
Palo Alto CA  94304-1126         FAX:   (650)-857-5100
Received on Tuesday, 21 January 2003 13:09:30 GMT

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