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

Re: Delta Compression and UTF-8 Header Values

From: Adrien W. de Croy <adrien@qbik.com>
Date: Sat, 09 Feb 2013 02:02:27 +0000
To: "James M Snell" <jasnell@gmail.com>, "Poul-Henning Kamp" <phk@phk.freebsd.dk>
Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-Id: <em4668684b-ed60-4859-8502-b238729278d9@bombed>

------ Original Message ------
From: "James M Snell" <jasnell@gmail.com>
To: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Sent: 9/02/2013 9:21:50 a.m.
Subject: Re: Delta Compression and UTF-8 Header Values
>On Feb 8, 2013 11:50 AM, "Poul-Henning Kamp" <phk@phk.freebsd.dk> 
> >

>If nothing else, it would be helpful to have a single encoding defined 
>for all non-ascii header field values that can be indicated by a bit 
>flag. E.g. if the flag is set, value is hex encoded binary. It doesn't 
>alleviate all the issues, of course, but  does simplify things for app 
do you mean just binary?  hex-encoded binary is just bloat for no good 
reason if your format is binary capable why would you double the size by 
hex-encoding it?


> > --
> > Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> > phk@FreeBSD.ORG         | TCP/IP since RFC 956
> > FreeBSD committer       | BSD since 4.3-tahoe
> > Never attribute to malice what can adequately be explained by 
Received on Saturday, 9 February 2013 02:03:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 9 February 2013 02:03:31 GMT