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

Re: HTTP/2 Header Encoding Status Update

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 27 Feb 2013 22:55:38 +0100
Message-ID: <512E80DA.2020802@gmx.de>
To: James M Snell <jasnell@gmail.com>
CC: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
On 2013-02-27 22:16, James M Snell wrote:
> As I'm not going to be able to meet y'all in Orlando, I wanted to give
> a quick status update on where I'm at with the Header Encoding.
>
> After much experimentation, implementation and discussion with
> Roberto, I've got an implementation that is a good balance between
> Delta and BOHE. It uses the fundamental delta encoding mechanism that
> Roberto created (with a few notable changes) but allows for four
> distinct types of header values: text, numeric, date and raw-binary.
> Every header value is encoded with a single additional byte flag that
> indicates the value type. Further, the flags indicate whether text is
> ISO-8559-1 or UTF-8 and whether it is huffman-coded or not.  This
> scheme gives us a good balance and allows us to achieve maximum
> compression ratios and increased long term functionality without
> sacrificing too much in complexity or backwards compatibility.
>
> Text values:
>
>    The rules for text values are simple:
>
>    1. Text can be either UTF-8 or ISO-8859-1 Encoded. A single bit in
> the flags is used to indicate which it is.

Why can't we stick to UTF-8 for text?

 > ...

Best regards, Julian
Received on Wednesday, 27 February 2013 21:56:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 February 2013 21:56:09 GMT