- From: David Krauss <potswa@gmail.com>
- Date: Wed, 16 Jul 2014 07:21:38 +0800
- To: Martin Thomson <martin.thomson@gmail.com>
- Cc: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>, Roberto Peon <grmocg@gmail.com>
What happened to WebSockets? Was a decision made off-list? Some means of flushing a stream is invaluable to interactive applications. A policy of one stream per request eats server (and intermediary) resources, and exhausts stream iDs. Don’t tell me that the traditional web isn’t interactive. Just because WebSockets aren’t yet widely deployed, doesn’t mean it isn’t the direction things are headed. HTTP/2 should be accelerating that process. On 2014–07–16, at 1:10 AM, Martin Thomson <martin.thomson@gmail.com> wrote: > On 14 July 2014 22:30, Mark Nottingham <mnot@mnot.net> wrote: >> It sounds like we've converged on getting rid of END_SEGMENT. I've marked it as editor-ready. > > Since we're removing affordances for websockets, can I handle #557 at > the same time. Not by adding METADATA, but by removing random, > semantic-free HEADERS frames. >
Received on Tuesday, 15 July 2014 23:22:10 UTC