Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues)

On Jul 18, 2014, at 3:13 PM, Michael Sweet <> wrote:

> Jason,
> On Jul 18, 2014, at 3:37 PM, Jason Greene <> wrote:
>> ...
>> I think hes referring to the encoding context update instruction in HPACK itself. So I guess you could just set the table to 0 and back to 4096 in the next HEADERS frame.
> OK, I read that section wrong then - it sounded like you could only reduce the size, not put it back up to the recipient's original limit.  Re-reading it now it makes sense; should this be stated explicitly in the HTTP/2 spec as the recommended re-synchronization procedure?

I added this info to the wiki as one of 3 options on dealing with compresses limits:

Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat

Received on Saturday, 19 July 2014 01:11:05 UTC