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

Re: structured headers "why not JSON" FAQ

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 13 Jun 2018 13:05:25 +0200
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
Cc: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <c15a0a05-728b-a045-2893-5e2c5ecab91c@gmx.de>
On 2018-06-13 12:17, Poul-Henning Kamp wrote:
> --------
> In message <9b4f808b-8586-d3ff-ffef-4e9fe48a725a@gmx.de>, Julian Reschke writes:
> 
>> I would say that the incentives are exactly the same for the two
>> variants. If the spec makes a mandatory requirement on the recipient
>> that is easy to implement, why would implementations choose to follow it
>> for SH but not for JFV?
> 
> Because with SH somebody underqualified won't stop reading at JSON and
> think he knows how this song goes and thus miss all the restrictions ?

In which case it won't work anyway, because you need to do 
<https://greenbytes.de/tech/webdav/draft-reschke-http-jfv-08.html#rfc.section.4> 
to get it working at all.

Best regards, Julian
Received on Wednesday, 13 June 2018 11:05:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:15:21 UTC