- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Fri, 15 Jul 2016 07:22:27 +0000
- To: Julian Reschke <julian.reschke@gmx.de>
- cc: Kazuho Oku <kazuhooku@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
-------- In message <a456ceb8-4b6e-a49f-02a0-6ebf3384ad8a@gmx.de>, Julian Reschke writes : >1) Mandate that all numeric values need to be transferred as strings >(loosing some of the benefits), or > >2) Require use of I-JSON (https://tools.ietf.org/html/rfc7493) >generators/parsers (loosing lots of potential implementations). I-JSON is probably the better of those two alternatives, despite the fact that the restrictions it mandates can be very hard to implement correctly and efficiently (in particular the unicode restrictions). The 3. alternative which you didn't list gets my vote: 3) Don't use JSON. -- 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 Friday, 15 July 2016 07:22:53 UTC