- From: David Krauss <potswa@gmail.com>
- Date: Tue, 22 Apr 2014 07:16:22 +0800
- To: HTTP Working Group <ietf-http-wg@w3.org>
One purpose of a small frame size, which led to CONTINUATION frames, is to ensure timely delivery of PRIORITY frames. (I would infer this applies, even more, to WINDOW_UPDATE.) But the CONTINUATION spec says they must form an uninterrupted chain after HEADERS, and that’s the same as just having one big frame. Do header blocks displace non-content-bearing frames such as PRIORITY, WINDOW_UPDATE, RST_STREAM, PING, and SETTINGS, or is there supposed to be an exception to the rule?
Received on Monday, 21 April 2014 23:17:01 UTC