Re: #537: Remove segments (consensus call)

Segments are not redundant with midstream headers.
Headers potentially have semantic meaning, even when 'empty'.

For my part, I still see that END_SEGMENT or something similar provides for
interesting characteristics for HTTP2->1 gateways in allowing chunks to be
reproduced (and we know that there are issues there) as well as allowing
the coalescing/tunneling of protocols such as WS onto the connection,
making them more viable.


On Tue, Jul 1, 2014 at 10:57 PM, David Krauss <> wrote:

> On 2014–07–02, at 1:02 PM, Mark Nottingham <> wrote:
> > It sounds like we're leaning towards removing it - can people live with
> that?
> As I noted in the other thread and on GitHub, segments are redundant with
> midstream headers. Both require data not to be coalesced across a boundary,
> and weakly suggest that intermediaries should flush. Neither work over
> HTTP/1.1.
> I have no complaint about removal, but “deprecation in favor” might be
> better terminology.

Received on Wednesday, 2 July 2014 06:12:54 UTC