W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2013

Re: The use of binary data in any part of HTTP 2.0 is not good

From: Mark Nottingham <mnot@mnot.net>
Date: Mon, 21 Jan 2013 10:48:30 +1100
Cc: William Chan (ι™ˆζ™Ίζ˜Œ) <willchan@chromium.org>, Pablo <paa.listas@gmail.com>, "HTTP Working Group" <ietf-http-wg@w3.org>
Message-Id: <7F8E363D-6D6E-4FDD-B8EA-24A31383B1A3@mnot.net>
To: "Adrien W. de Croy" <adrien@qbik.com>

On 21/01/2013, at 10:38 AM, "Adrien W. de Croy" <adrien@qbik.com> wrote:

> 
> the thing that will make debugging harder won't be binary vs text, but the inter-dependence of messages.  Especially when it comes to looking through debug logs for issues.
> 
> On-the-wire, you already need to piece together a TCP stream to see what's going on, so having http messages effectively split over multiple frames (e.g. delta encoding, or compression) only becomes a problem when you don't capture enough to decode.
> 
> I think it might be worth-while specifying a requirement for a "debug" option for senders of binary messages which turns off all other optimisations, such as caching unchanged headers etc (so they are sent every time).  Just an idea.

That's been brought up a few times, and the reaction has been pretty positive.

Cheers,


--
Mark Nottingham   http://www.mnot.net/
Received on Sunday, 20 January 2013 23:48:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 20 January 2013 23:48:56 GMT