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

Re: END_SEGMENT? (#397)

From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 18 Jun 2014 12:19:50 -0700
Message-ID: <CABkgnnXbz5GqSrgdf5Hsoqbjh7HSPHmB+PtCNmRafXCTS=0N3g@mail.gmail.com>
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.

Received on Wednesday, 18 June 2014 19:20:17 UTC

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