- From: Roy T. Fielding <fielding@gbiv.com>
- Date: Thu, 17 Apr 2014 22:35:21 -0700
- To: Jeff Pinner <jpinner@twitter.com>
- Cc: K.Morgan@iaea.org, HTTP Working Group <ietf-http-wg@w3.org>, C.Brunhuber@iaea.org
On Apr 17, 2014, at 9:25 AM, Jeff Pinner wrote: > 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. FWIW, that won't work in HTTP/1.1 (intermediaries and network libraries will consume and coalesce chunks before any application gets to see them). ....Roy
Received on Friday, 18 April 2014 05:35:46 UTC