- From: Kulkarni, Saurabh <sakulkar@akamai.com>
- Date: Thu, 17 Apr 2014 18:20:10 -0400
- To: HTTP Working Group <ietf-http-wg@w3.org>
Received on Thursday, 17 April 2014 22:20:38 UTC
Does a “Encoding Context Update” require a indexed representation with ‘0’ index and then a “001 <command>” or this is just an editorial mistake in not deleting this part of the spec. So: This is the description for Indexed Representation: An _indexed representation_ with an index value of 0 entails one of the following actions, depending on what is encoded next: o The reference set is emptied. o The maximum size of the header table is updated. And this is description for Encoding context update: An encoding context update causes the immediate application of a change to the encoding context. +---+---+---+---+---+---+---+---+ | 0 | 0 | 1 | F | ... | +---+---------------------------+ Context Update An encoding context update starts with the ’001’ 3-bit pattern. But doesn’t really mention indexed representation. Based on the bits used, I am guessing the indexed representation was not updated? Please clarify, thanks. - Saurabh
Received on Thursday, 17 April 2014 22:20:38 UTC