Re: Header Serialization Discussion

"Adrien W. de Croy" <adrien@qbik.com> Mon, 15 April 2013 23:44 UTC

Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FC5D21F93E2 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 15 Apr 2013 16:44:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7+XQdb7+QtBU for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 15 Apr 2013 16:44:56 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id A9EA521F93CD for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 15 Apr 2013 16:44:56 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1URt4e-0006sX-47 for ietf-http-wg-dist@listhub.w3.org; Mon, 15 Apr 2013 23:44:36 +0000
Resent-Date: Mon, 15 Apr 2013 23:44:36 +0000
Resent-Message-Id: <E1URt4e-0006sX-47@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <adrien@qbik.com>) id 1URt4c-0006rn-9o for ietf-http-wg@listhub.w3.org; Mon, 15 Apr 2013 23:44:34 +0000
Received: from smtp.qbik.com ([210.55.214.35]) by lisa.w3.org with esmtp (Exim 4.72) (envelope-from <adrien@qbik.com>) id 1URt4a-0007Rp-AC for ietf-http-wg@w3.org; Mon, 15 Apr 2013 23:44:34 +0000
Received: From [192.168.0.10] (unverified [192.168.0.10]) by SMTP Server [192.168.0.1] (WinGate SMTP Receiver v8.0.0 (Build 3530)) with SMTP id <0019650379@smtp.qbik.com>; Tue, 16 Apr 2013 11:44:08 +1200
From: "Adrien W. de Croy" <adrien@qbik.com>
To: James M Snell <jasnell@gmail.com>, RUELLAN Herve <Herve.Ruellan@crf.canon.fr>
Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Date: Mon, 15 Apr 2013 23:44:08 +0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; format="flowed"; charset="utf-8"
In-Reply-To: <CABP7Rbcvqas52h8hJatDgqVQsnH3dHAkZREHTLU=ADKbx=0uSQ@mail.gmail.com>
Message-Id: <eme0b11005-a323-4146-8d02-757c869c5920@bombed>
Mime-Version: 1.0
Reply-To: "Adrien W. de Croy" <adrien@qbik.com>
User-Agent: eM_Client/5.0.17595.0
Received-SPF: pass client-ip=210.55.214.35; envelope-from=adrien@qbik.com; helo=smtp.qbik.com
X-W3C-Hub-Spam-Status: No, score=-4.7
X-W3C-Hub-Spam-Report: AWL=-2.212, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.556, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1URt4a-0007Rp-AC 1d299959ee800b2e236f464382061ab7
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Header Serialization Discussion
Archived-At: <http://www.w3.org/mid/eme0b11005-a323-4146-8d02-757c869c5920@bombed>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/17242
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

------ Original Message ------
From: "James M Snell" <jasnell@gmail.com>
>On Mon, Apr 15, 2013 at 8:28 AM, RUELLAN Herve
><Herve.Ruellan@crf.canon.fr> wrote:
>>
>>[snip]
>>>
>>>    - The true utility of the common prefix length mechanism is 
>>>questionable.
>>>  Aside from the potential security risks, I questioning just how 
>>>effective it's
>>>  going to be in practice. (What header fields do we expect to 
>>>actually use it in
>>>  practice?)
>>
>>  Common prefixes are very efficient for URLs: the paths often share 
>>some common part at their beginnings. They are also useful for other 
>>type of data such a date and integers, but these could be optimized 
>>using typed codecs.
>>
>
>I generally prefer the typed codecs for dates and integers. I'm
>struggling to see what, beyond URLs, the prefixes will be useful for,
>really. I mean, I get the theory, I understand their use, but I'm just
>not convinced how often it will be practical outside of the request
>URI.

Referer as well



Adrien

>
>