W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2014

Re: agenda/charter brainstorming

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 23 Jun 2014 20:23:16 +0200
Message-ID: <53A87094.6030205@gmx.de>
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
CC: James M Snell <jasnell@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
On 2014-06-23 19:44, Poul-Henning Kamp wrote:
> In message <53A84F41.9000501@gmx.de>, Julian Reschke writes:
>> On 2014-06-23 17:53, James M Snell wrote:
>>> On Mon, Jun 23, 2014 at 1:43 AM, Julian Reschke <julian.reschke@gmx.de> wrote:
>
>>>> - Header field syntax is something people continue to struggle with; maybe
>>>> define how to use JSON in header fields to make things easier for new header
>>>> field definitions
>>>
>>> +1 ... but I would frame the problem differently: Existing header
>>> syntax is inefficient, inconsistent and incomplete at best. [...]
>
>> I'm looking for something that works across all HTTP versions, so binary
>> IMHO is out.
>
> As long as a loss-less conversion exists, that's needlessly strict.
>
> For instance Date: can trivially be converted to an integer and back
> without any loss of information.

We're talking past each other.

I'm talking about a generic field format for new header fields. You are 
talking about different ways to serialize existing header fields.

Best regards, Julian
Received on Monday, 23 June 2014 18:23:57 UTC

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