- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 11 Jul 2016 08:09:02 +0200
- To: Martin Thomson <martin.thomson@gmail.com>
- Cc: Kazuho Oku <kazuhooku@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>, Stefan Eissing <stefan.eissing@greenbytes.de>
On 2016-07-11 06:09, Martin Thomson wrote:
> On 9 July 2016 at 03:18, Julian Reschke <julian.reschke@gmx.de> wrote:
>> "gzip", {"identity": {"q": 0.5}}, {"*": {"q": 0}}
>
> If you accept that each value is a json value, then this is OK, but I
> think that I'd prefer simply:
> A-E: { "gzip": {}, "identity": {"q":0.5}, "*": {"q":0} }
> The drawback being that you can't include gzip twice in this form.
> That's probably a virtue. See also PHK's comments here.
That's one of the things we need to decide: whether to default to a
container format (object vs list) or not:
1) If we default to a list, the format will be consistent with multiple
header field instances with no extra work.
2) If we default to object, you could use the notation above, but loose
the list behavior.
3) If do not default at all, we'll either always have more delimiters on
the wire, or need to define heuristics so the recipient knows what to do
before invoking the JSON parser.
(The draft currently chooses 1)
Best regards, Julian
Received on Monday, 11 July 2016 06:09:35 UTC