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

Re: HTTP/1.1 : Chunking

From: Jeffrey Mogul <mogul@pa.dec.com>
Date: Thu, 29 Jan 98 14:12:15 PST
Message-Id: <9801292212.AA05992@acetes.pa.dec.com>
To: http-wg@cuckoo.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/5316
John Franks writes:
    Chunking has very low overhead.  From the point of view of efficiency
    there would be no problem for clients or servers if ALL transactions
    were required to be chunked.  There is not much performance difference
      Content-length: 123456
	  <123456 bytes of data>
      Content-encoding: chunked
	  <123456 bytes of data>
Unfortunately, there is a slight correctness difference here!

>From 3.6.1, "The chunk-size field is a string of hex digits"
so the correct form is

      Content-encoding: chunked

          <123456 bytes of data>

Otherwise, I agree entirely with John.  (And note that parsing
hex numbers is usually less expensive than parsing decimals,
by a few instruction cycles.)

Received on Thursday, 29 January 1998 14:13:35 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:04 UTC