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

Re: END_SEGMENT? (#397)

From: Jeff Pinner <jpinner@twitter.com>
Date: Thu, 19 Jun 2014 10:26:10 -0700
Message-ID: <CA+pLO_gZF5w+1BC9ZqEQTL4E1-Uv1JXRi=zErQ7=WEtstixyHg@mail.gmail.com>
To: Daniel Sommermann <dcsommer@fb.com>
Cc: Yutaka Hirano <yhirano@google.com>, Martin Thomson <martin.thomson@gmail.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>
>
>
> Both options require changes. Even if the intermediary doesn't understand
> WS, normal day-to-day HTTP/1.1 APIs would have to change to accommodate
> segments. In my mind, that is nearly the same as requiring the proxy to
> understand WS.
>
>
The requirements as written were done so that there is no to change normal
day-to-day HTTP/1.1 APIs. It is a requirement on the framing layer, not the
HTTP message layer.

This is in the same sense as HTTP/1.1 APIs do not need to be changed to
understand PING or SETTINGS.
Received on Thursday, 19 June 2014 17:26:41 UTC

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