W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > January to April 1998

Re: HTTP/1.1 : Chunking

From: David W. Morris <dwm@xpasc.com>
Date: Thu, 29 Jan 1998 13:02:07 -0800 (PST)
To: John Franks <john@math.nwu.edu>
Cc: Adrien de Croy <adrien@qbik.com>, http-wg@cuckoo.hpl.hp.com
Message-Id: <Pine.GSO.3.96.980129130049.16269I-100000@shell1.aimnet.com>


On Thu, 29 Jan 1998, John Franks wrote:

> On Thu, 29 Jan 1998, Adrien de Croy wrote:
> > 
> > 1. The chunk size may be arbitrary, and the resulting latency introduced at
> > the server (since chunking at the server requires some form of buffering)
> > may cause performance degradation in applications such as streamed media
> > through HTTP.  Is there any recommendation on how to chunk the data?
> > 
> 
> The server may chunk anyway it chooses.  It can choose to do so in a
> way it finds most efficient.
> 
> > 2. Any intermediary (proxy) must continually monitor the transfer through
> > itself. Is it allowed to re-chunk the data, and if so under what guidelines.
> > 
> 
> It is not only allowed, but expected to be the most common practice
> for caching proxies.  The proxy can re-chunk anyway it chooses.

And required to be removed when forwarding the response to an HTTP/1.0
client.

Dave Morris
Received on Thursday, 29 January 1998 13:05:21 EST

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:33:11 EDT