Re: Abbreviation form for HTTP JSON Header Field Values?

--------
In message <a35a491a-70a5-81a1-719e-a308a730fc2b@gmx.de>, Julian Reschke writes
:

>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)

I vote strongly for 3 with the "always have more delimiteres on the wire"
option:  Don't straight-jacket the people who have to define new headers.

-- 
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.

Received on Monday, 11 July 2016 09:34:22 UTC