- From: Patrick McManus <pmcmanus@mozilla.com>
- Date: Tue, 23 Jul 2013 17:00:39 -0400
- To: HTTP Working Group <ietf-http-wg@w3.org>
- Message-ID: <CAOdDvNoTsJn-MqdpTG7viHXWwRcA-v+rePVZCRkWUALM_2vgBg@mail.gmail.com>
I found this really confusing: SETTINGS_FLOW_CONTROL_OPTIONS (10): indicates that streams directed to the sender will not be subject to flow control. The least significant bit (0x1) of the value is set to indicate that new streams are not flow controlled. All other bits are reserved. This setting applies to all streams, including existing streams. These bits cannot be cleared once set, see Section 6.9.4 <http://tools.ietf.org/html/draft-ietf-httpbis-http2-04#section-6.9.4>. 1] does the value always need to be 1? The option as a whole is defined to indicate that "streams .. will not be subject to flow control" - so not setting the value would seem to be inconsistent. But if the value can only be 1, why define a value at all? Maybe the option definition is misleading and should be "whether or not streams will be subject to flow control"? 2] "This setting applies to all streams, including existing ones".. but the "value is set to indicate that new streams are not flow controlled" (implying existing streams are not impacted). 3] "These bits cannot be..".. bits is plural, but only 1 bit is defined. barring better advice, for my -04 implementation I am going to test the low bit of the value, and if true apply the logic to all present and future sends directed to the sender of the option.
Received on Tuesday, 23 July 2013 21:01:07 UTC