- From: Jeff Pinner <jpinner@twitter.com>
- Date: Thu, 17 Apr 2014 09:25:31 -0700
- To: K.Morgan@iaea.org
- Cc: HTTP Working Group <ietf-http-wg@w3.org>, C.Brunhuber@iaea.org
Received on Thursday, 17 April 2014 16:26:00 UTC
On Thu, Apr 17, 2014 at 12:52 AM, <K.Morgan@iaea.org> wrote: > > What is the purpose of END_SEGMENT? > > > END_SEGMENTS allows the layering of record-based semantics onto the framing layer. Consider this use case in HTTP/1.1. An API provides a stream of data using HTTP/1.1 chunked encoding. Each chunk contains a single record, and the length of this record is indicated by the chunk length. In HTTP/1.1 the length of these chunks was unconstrained, but when translating into HTTP/2, these chunks must be segmented into multiple data frames to fit within the frame size limit. If the chunk delineation was meaningful, then END_SEGMENT allows this meaning to be preserved. The flag is also useful for layering other record-based protocols on top of HTTP.
Received on Thursday, 17 April 2014 16:26:00 UTC