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


From: <K.Morgan@iaea.org>
Date: Thu, 17 Apr 2014 20:00:59 +0000
To: <jpinner@twitter.com>
CC: <ietf-http-wg@w3.org>, <C.Brunhuber@iaea.org>
Message-ID: <39020B86-7C94-4CBB-8D45-72034905BA99@iaea.org>
I think the first paragraph from Jeff's explanation below should be added to the spec as an explanation of the purpose of END_SEGMENT. Perhaps more.

On Apr 17, 2014, at 18:29, "jpinner@twitter.com<mailto:jpinner@twitter.com>" <jpinner@twitter.com<mailto:jpinner@twitter.com>> wrote:

On Thu, Apr 17, 2014 at 12:52 AM, <K.Morgan@iaea.org<mailto: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.

This email message is intended only for the use of the named recipient. Information contained in this email message and its attachments may be privileged, confidential and protected from disclosure. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others. Also please notify the sender by replying to this message and then delete it from your system.
Received on Thursday, 17 April 2014 20:01:35 UTC

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