W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2014

END_SEGMENT and headers

From: David Krauss <potswa@gmail.com>
Date: Wed, 16 Apr 2014 12:54:06 +0800
Message-Id: <9E37B592-C957-45BC-AD4D-97D11768E711@gmail.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
The END_SEGMENT flag is defined for HEADERS frames, but it seems to be meaningless. A literal reading of the draft seems to say that such a frame cannot be coalesced with subsequent CONTINUATION frames, but those frames do not also have the same (useless) segmentation capability.

Why not let END_SEGMENT and END_HEADERS be the same bit? Then headers be treated as the first segment of any stream, by some simplistic intermediaries. It also reclaims a flag bit, as they are running into short supply.

Also, is END_SEGMENT required when END_STREAM is set? It seems it should be, for the sake of protocol regularity.
Received on Wednesday, 16 April 2014 04:54:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:29 UTC