- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Wed, 18 Jun 2014 12:19:50 -0700
- To: Daniel Sommermann <dcsommer@fb.com>
- Cc: Mike Bishop <Michael.Bishop@microsoft.com>, Jeff Pinner <jpinner@twitter.com>, "K.Morgan@iaea.org" <K.Morgan@iaea.org>, HTTP Working Group <ietf-http-wg@w3.org>, "C.Brunhuber@iaea.org" <C.Brunhuber@iaea.org>
On 18 June 2014 09:44, Daniel Sommermann <dcsommer@fb.com> wrote: > Yes, this is precisely what I was getting at with the layering issue I > brought up. It seems like a layering violation to expose segments to the > application. It also doesn't map to HTTP/1.1 concepts (I don't see how it > maps to chunked encoding since there is no chunk length). This seems like an > example of a feature in the protocol that is not backwards compatible with > HTTP/1.1. In this case, the incompatibility is at the API level, not the > semantic level. https://github.com/http2/http2-spec/issues/537
Received on Wednesday, 18 June 2014 19:20:17 UTC