W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2012

Re[2]: FYI... Binary Optimized Header Encoding for SPDY

From: Adrien de Croy <adrien@qbik.com>
Date: Fri, 03 Aug 2012 21:05:53 +0000
To: "James M Snell" <jasnell@gmail.com>, "Zhong Yu" <zhong.j.yu@gmail.com>
Cc: Martin J. Dürst <duerst@it.aoyama.ac.jp>, "Poul-Henning Kamp" <phk@phk.freebsd.dk>, "Mike Belshe" <mike@belshe.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-Id: <em3ff60a6d-dd6e-4747-9648-17256e5f8332@reboist>

------ Original Message ------
From: "James M Snell" <jasnell@gmail.com>
To: "Zhong Yu" <zhong.j.yu@gmail.com>
Cc: "Adrien W. de Croy" <adrien@qbik.com>;"Martin J. Dürst" 
<duerst@it.aoyama.ac.jp>;"Poul-Henning Kamp" <phk@phk.freebsd.dk>;"Mike 
Belshe" <mike@belshe.com>;"ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Sent: 4/08/2012 5:11:53 a.m.
Subject: Re: FYI... Binary Optimized Header Encoding for SPDY
>+1... at the HTTP level, we should not be trying to split up the 
>request URI like this. Treat it like an opaque string...
>Besides, there are MANY applications that mix application specific 
>parameters into the path as well as the query string, so splitting 
>those up to protect privacy doesn't really make any sense at all.

I wasn't suggesting it as a privacy thing.

Merely as a way to avoid string parsing, which necessitates escaping, 
which reduces performance, and introduces other problems.

Received on Friday, 3 August 2012 21:06:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:03 UTC