Re: Large Frames, Continuations, Flow Control, and changing HPACK from Jeff Pinner on 2014-07-08 (ietf-http-wg@w3.org from July to September 2014)

From: Jeff Pinner <jpinner@twitter.com>
Date: Tue, 8 Jul 2014 10:47:09 -0700
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Cory Benfield <cory@lukasa.co.uk>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <CA+pLO_gth9=v7ykb=fPRW3c4cCtVKTC2UNYB6+XOi-Vn7+zFHw@mail.gmail.com>

> For some sets of data.  The samples we have are for browsing and only
> for very short sessions.  For APIs, server-to-server,
> XmlHTTPRequest-heavy pages, and similar, my understanding is that a
> reference set would be a significant improvement.  I believe that the
> reference set would have represented a significant improvement in the
> applications I was building when I was at Microsoft.  Sadly, I can't
> run the numbers to support this claim.

I am not suggesting we remove the header table, so you can still
encode header fields using the "indexed representation." Yes it is
less efficient than requiring 0 bytes, but in most cases you should be
abel to get away with encoding it in 1 or 2 bytes.

Received on Tuesday, 8 July 2014 17:47:37 UTC