- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Fri, 17 Jan 2014 09:02:50 +0000
- To: "Nicolas Mailhot" <nicolas.mailhot@laposte.net>
- cc: "Zhong Yu" <zhong.j.yu@gmail.com>, "Julian Reschke" <julian.reschke@gmx.de>, "Gabriel Montenegro" <gabriel.montenegro@microsoft.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>, "Osama Mazahir" <osamam@microsoft.com>, "Dave Thaler" <dthaler@microsoft.com>, "Mike Bishop" <michael.bishop@microsoft.com>, "Matthew Cox" <macox@microsoft.com>
In message <aba0c024677d0d0bf4dc944ef64da6b7.squirrel@arekh.dyndns.org>, "Nicol as Mailhot" writes: >I'd rather have clear interop rules and simple to understand breakage at >http2 adoption time rather than diffuse heisenbugs and sites that work by >sheer chance as long as you chain components with the same unwritten >assumptions. See the python 2 unicode debacle and how much fuzzy encoding >rules cost them. Seconded. This is one clear way HTTP/2 can improve over HTTP/1.1: Eliminate unnecessary and pointless fuzziness. -- 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, 17 January 2014 09:03:15 UTC