Re: If not JSON, what then ?

"Poul-Henning Kamp" <phk@phk.freebsd.dk> Mon, 01 August 2016 10:02 UTC

Resent-Date: Mon, 01 Aug 2016 09:57:54 +0000
Resent-Message-Id: <E1bU9ys-0006mX-0P@frink.w3.org>
To: HTTP Working Group <ietf-http-wg@w3.org>, Willy Tarreau <w@1wt.eu>
In-reply-to: <20160801085743.GB22715@1wt.eu>
From: Poul-Henning Kamp <phk@phk.freebsd.dk>
References: <77778.1470037414@critter.freebsd.dk> <20160801085743.GB22715@1wt.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <84603.1470045445.1@critter.freebsd.dk>
Date: Mon, 01 Aug 2016 09:57:25 +0000
Message-ID: <84604.1470045445@critter.freebsd.dk>
Received-SPF: none client-ip=130.225.244.222; envelope-from=phk@phk.freebsd.dk; helo=phk.freebsd.dk
Subject: Re: If not JSON, what then ?
Archived-At: <http://www.w3.org/mid/84604.1470045445@critter.freebsd.dk>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

--------
In message <20160801085743.GB22715@1wt.eu>, Willy Tarreau writes:

>That made me think that most of the header fields I'm seeing do not use
>non-ascii characters at all, I'd even say non-printable-ascii. Most of
>them contain :
>  - host names (Host)
>  - uris (Referer, Location)
>  - user-agent strings (UA)
>  - tokens (Connection, Accept, ...)
>  - numbers
>
>Thus in fact I'm wondering if it's really worth focusing the efforts on
>non-ascii strings instead.

My take is that the data-model and serialization should be general
and unconstrained, and the constraints be applied in a/the schema
for each individual header.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

Re: If not JSON, what then ? Sam Johnston
Re: If not JSON, what then ? Martin J. Dürst
Re: If not JSON, what then ? Alcides Viamontes E
Re: If not JSON, what then ? Mark Nottingham
Re: If not JSON, what then ? Willy Tarreau
Re: If not JSON, what then ? Poul-Henning Kamp
Re: If not JSON, what then ? Martin Thomson
Re: If not JSON, what then ? Poul-Henning Kamp
Re: If not JSON, what then ? Mark Nottingham
Re: If not JSON, what then ? Poul-Henning Kamp
Re: If not JSON, what then ? Martin Thomson
Re: If not JSON, what then ? Willy Tarreau
Re: If not JSON, what then ? Kari hurtta
Re: If not JSON, what then ? Willy Tarreau
Re: If not JSON, what then ? Poul-Henning Kamp
Re: If not JSON, what then ? Kari hurtta
Re: If not JSON, what then ? Martin Thomson
Re: If not JSON, what then ? Carsten Bormann
Re: If not JSON, what then ? Poul-Henning Kamp
Re: If not JSON, what then ? Mark Nottingham
Re: If not JSON, what then ? Carsten Bormann
Re: If not JSON, what then ? Poul-Henning Kamp
Re: If not JSON, what then ? Carsten Bormann
Re: If not JSON, what then ? Poul-Henning Kamp
Re: If not JSON, what then ? Stefan Eissing
Re: If not JSON, what then ? Willy Tarreau
Re: If not JSON, what then ? nicolas.mailhot
Re: If not JSON, what then ? Poul-Henning Kamp
Re: If not JSON, what then ? Mark Nottingham
Re: If not JSON, what then ? Poul-Henning Kamp
Re: If not JSON, what then ? Mark Nottingham
Re: If not JSON, what then ? Mark Nottingham
Re: If not JSON, what then ? nicolas.mailhot
Re: If not JSON, what then ? Poul-Henning Kamp
Re: If not JSON, what then ? Stefan Eissing
Re: If not JSON, what then ? Poul-Henning Kamp
Re: If not JSON, what then ? Poul-Henning Kamp
Re: If not JSON, what then ? Willy Tarreau
Re: If not JSON, what then ? Mark Nottingham
Re: If not JSON, what then ? James M Snell
Re: If not JSON, what then ? Cory Benfield
Re: If not JSON, what then ? Poul-Henning Kamp
Re: If not JSON, what then ? Poul-Henning Kamp
Re: If not JSON, what then ? Willy Tarreau
Re: If not JSON, what then ? Nicolas Mailhot
Re: If not JSON, what then ? Poul-Henning Kamp
Re: If not JSON, what then ? Poul-Henning Kamp
Re: If not JSON, what then ? Willy Tarreau
Re: If not JSON, what then ? Carsten Bormann
If not JSON, what then ? Poul-Henning Kamp