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: Mon, 30 Jun 2014 10:01:07 -0700
Message-ID: <CABkgnnUsCS3P0ZR-vDyeTzTu2nRKF06cLybvgQbisAWiRqo+8w@mail.gmail.com>
To: David Krauss <potswa@gmail.com>
Cc: Daniel Sommermann <dcsommer@fb.com>, HTTP Working Group <ietf-http-wg@w3.org>
On 30 June 2014 09:54, David Krauss <potswa@gmail.com> wrote:
> “Tackle”? It’s an editorial issue, and reviewing GitHub it essentially boils down to specifying what sort of flush should occur.
>
> I don’t think anyone’s talking about removing END_SEGMENT or WebSocket support. It’s essential to interactive applications, including the sort of things that WebSockets often does. This is something all proxies should handle going forward.

I think that people are.  From some perspectives, END_SEGMENT is cruft
and WebSocket support isn't present.  From the other perspective,
thewebsocketprotocol can be shoehorned in and that's good enough.
Received on Monday, 30 June 2014 17:01:34 UTC

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