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

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

From: John J. Barton <John_Barton@hpl.hp.com>
Date: Wed, 29 Jan 2003 12:57:43 -0800
Message-Id: <>
To: "Sanjiva Weerawarana" <sanjiva@watson.ibm.com>, "Jeffrey Schlimmer" <jeffsch@windows.microsoft.com>, <jones@research.att.com>
Cc: <xml-dist-app@w3.org>

At 11:41 AM 1/29/2003 +0600, Sanjiva Weerawarana wrote:

> > DR19. The specification must enable efficient allocation of buffers by
> > receivers.
>I'm again confused; while a statement like "this spec must be
>implementable as efficiently as possible" is reasonable (and
>motherhood-and-apple-pie IMO), speaking specifically about
>buffer allocation seems rather pointed.

Sanjiva, the key words here are "by receivers".  The serialization
mechanism can have serious impacts on resource constrained or
heavily loaded receivers.  Emitting a SOAP message in an
HTTP-style MIME-like format without content-length headers leaves
the receiver with no  recourse but multiple buffering layers and repeated
dynamic memory allocations as more content arrives.  For resource
constrained receivers, the result is late and annoying buffer overflow;
for heavily loaded receivers, the result is poor performance.

This is, unfortunately not apple-pie since typically a receiver-friendly
protocol requires resources to be spent on the sender, eg to count
the bytes as the package is assembled.  The specification will
shift real costs.

Hope this helps clarify this issue.


John J. Barton          email:  John_Barton@hpl.hp.com
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 Wednesday, 29 January 2003 15:57:49 UTC

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