Re: HTTP/2 and Websockets
Yutaka Hirano <yhirano@google.com> Fri, 21 November 2014 04:37 UTC
Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E4AF1AD0A5 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 20 Nov 2014 20:37:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.973
X-Spam-Level:
X-Spam-Status: No, score=-6.973 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Diz6XtIQaZxx for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 20 Nov 2014 20:37:19 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C2751AD05E for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 20 Nov 2014 20:37:18 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1XrfvR-0004JM-JH for ietf-http-wg-dist@listhub.w3.org; Fri, 21 Nov 2014 04:34:29 +0000
Resent-Date: Fri, 21 Nov 2014 04:34:29 +0000
Resent-Message-Id: <E1XrfvR-0004JM-JH@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <yhirano@google.com>) id 1XrfvC-0004Gh-TE for ietf-http-wg@listhub.w3.org; Fri, 21 Nov 2014 04:34:14 +0000
Received: from mail-yk0-f171.google.com ([209.85.160.171]) by lisa.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <yhirano@google.com>) id 1Xrfv9-0004W4-6B for ietf-http-wg@w3.org; Fri, 21 Nov 2014 04:34:14 +0000
Received: by mail-yk0-f171.google.com with SMTP id 142so1946662ykq.16 for <ietf-http-wg@w3.org>; Thu, 20 Nov 2014 20:33:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GBcf8NQzzxQPyoXSpbCuSaCql7te7TyOpvrs6IwWJ1k=; b=oFzZNu/AHsNzls3K/ywFTwfEyvdUtiKQnVXQJdnlRtqp/8o8TTk7LR4AYI3fgt75Ch dXZlmZOh5DIxYxwItVjKMNgTzaVdSX916FB125lp7KwDT8N36H9+JZhnwcP2pMT4fstg 0B1+Q60EkIquiMmPW5liGmRJW8FD81dGTjrHvS2W3mKYIZvWeZFJMm5HWQr7Qbqnt2kA mJs8j12cepOrzL8V4kdMZ/ZfRi2EkeKkGBsYLE3BZWbT/NR3yqM04SzvP0+f5AGziZrL ZYJB4mgkm3J8QTT+ZJcSfixIGpPZwTjve14QPWGpc7gcTEeZVtqfDEzONW4AaahRGU68 bqDA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=GBcf8NQzzxQPyoXSpbCuSaCql7te7TyOpvrs6IwWJ1k=; b=UbIEEQemcKxODkH3o4whiWMB+AGPG73ZF2RePm8R4VtJ+OIE8qfp8IILC/RgYOYphX S11E7POJIrIBRKOz7NuhFizcWj6jcyX+69Qj/VoSVchTSFob4iKGUuaTTs9O1XK+0n5P dEEmNoGFXNwdBSG3v1AveYe5/galAGfUQFhI9ESaybzr5Bzt0bsMjTaLwIRIV9rKM5NM Z8EMwzCyXU9KdkPVf/mDlIG0n/mrbL2fut2Qq+o9eG5PI/ULbusooqEwat6o3f0f/vt+ B6CSHDLrrJjjf36UjugssAbKAqL0d2lXYAzQmb+Kx4w7oB3zrK9XBxF6jBgTvqw4UaKC UI+g==
X-Gm-Message-State: ALoCoQnK7+CaN1lGIhsRyRQUYNlvxjRGXRpHgku1w+vp8OTuhNZVvBn1eml9dU/5/HXHpBLwpQGi
MIME-Version: 1.0
X-Received: by 10.236.209.229 with SMTP id s65mr238741yho.128.1416544425250; Thu, 20 Nov 2014 20:33:45 -0800 (PST)
Received: by 10.170.196.14 with HTTP; Thu, 20 Nov 2014 20:33:45 -0800 (PST)
In-Reply-To: <5935365C-7FE7-4BDC-87B7-B287C9EF53C8@warmcat.com>
References: <CAJ3HoZ1gHH1MmY=NY68HBcFV7u74qKtkdWDe4i93MkjnXE+sPg@mail.gmail.com> <CABihn6GAu7pViZ3JxHAm1-SOeFLvxOQAuhrzwROGGY2jiCg4Cg@mail.gmail.com> <CAJ3HoZ3wfFMT2=duF22FyQGgdPzJwfmSSw0t82c9uvTkcsm1wg@mail.gmail.com> <CABihn6FwK7uZpg6v7u9byTw6xNsTjFsWfv_QyPMReTtumaXJWA@mail.gmail.com> <542BD960.7020407@treenet.co.nz> <CAJ3HoZ1B5hGrhzAnVYnDbYWV_BPmqMKsOhvM7VvS+2xFNT7krw@mail.gmail.com> <543D024D.2070001@treenet.co.nz> <CAJ3HoZ0aRLhB4Pf3zZobrzZYqYK8FguqMpNEvqoJ82FyM_XKHg@mail.gmail.com> <6D965D58-91C9-4DE0-AA2F-7559C0594368@warmcat.com> <CABihn6FPAWKABgJKHYNg5f1hOZsUTngKnhBkaB6cCNkG75cWCw@mail.gmail.com> <53882B6B-244E-4ADF-95DB-2E9DC4542C21@warmcat.com> <CABihn6E9OBTxSVvLHmhiwXcmwrDCo8w2DbYJwaNCaYvjSjUZqw@mail.gmail.com> <7597002B-B6DE-49FC-9B25-741D5130569F@warmcat.com> <5935365C-7FE7-4BDC-87B7-B287C9EF53C8@warmcat.com>
Date: Fri, 21 Nov 2014 13:33:45 +0900
Message-ID: <CABihn6Hmpb=y1pbg6OjV2jrwzFN1Crg7kQrPPzREbCRQEvf51A@mail.gmail.com>
From: Yutaka Hirano <yhirano@google.com>
To: Andy Green <andy@warmcat.com>
Cc: Robert Collins <robertc@robertcollins.net>, Amos Jeffries <squid3@treenet.co.nz>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="001a11c1c3a446bf4f050856f3f4"
Received-SPF: pass client-ip=209.85.160.171; envelope-from=yhirano@google.com; helo=mail-yk0-f171.google.com
X-W3C-Hub-Spam-Status: No, score=-3.4
X-W3C-Hub-Spam-Report: AWL=-2.580, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01
X-W3C-Scan-Sig: lisa.w3.org 1Xrfv9-0004W4-6B ab58fccf79383b767d7a53a711db2e21
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTP/2 and Websockets
Archived-At: <http://www.w3.org/mid/CABihn6Hmpb=y1pbg6OjV2jrwzFN1Crg7kQrPPzREbCRQEvf51A@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/28072
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
> > - WSDATA's 8-bit flags field, is the ws flags [fin][rsv1-3][opcode] We may want END_STREAM as well. Corresponding http2 frames can substitue ping / pong / close (note: WebSocket ones have payload though h2 ones don't). Shoud we have opcodes for them? On Fri, Nov 21, 2014 at 1:13 PM, Andy Green <andy@warmcat.com> wrote: > > > On 21 November 2014 11:38:26 GMT+08:00, Andy Green <andy@warmcat.com> > wrote: > > > > > >On 21 November 2014 11:30:46 GMT+08:00, Yutaka Hirano > ><yhirano@google.com> wrote: > >>On Fri, Nov 21, 2014 at 11:42 AM, Andy Green <andy@warmcat.com> wrote: > >> > >>> > >>> > >>> On 21 November 2014 10:02:28 GMT+08:00, Yutaka Hirano > >><yhirano@google.com> > >>> wrote: > >>> >> > >>> >> I think you have to take the atomic large ws frame thing as a > >>genuine > >>> >> problem because http2 has the transmit credit concept. So even > >if > >>> >you > >>> >> buffered one ws frame, you can't sit there spewing as much http2 > >>DATA > >>> >frame > >>> >> as it needs to atomically encapsulate it, without sizing your > >>http2 > >>> >frame > >>> >> to suit the tx credit. > >>> >> But it's OK because the implementation can transparently fragment > >>the > >>> >ws > >>> >> data using the ws message semantics... I think there's no choice > >>but > >>> >to > >>> >> take that approach. > >>> > > >>> >Sorry I don't understand what you are proposing. Can you explain? > >>> > >>> I'm agreeing with what was already written by someone else on the > >>thread. > >>> > >>> Talking about buffering huge ws frames until you have enough to > >issue > >>it > >>> all in one big http2 DATA frame will not fly. > >>> > >>> If you're using this putative ws-over-http2 scheme, and you get > >given > >>a > >>> huge ws frame to transmit, you should fragment it using RFC6455 > >>message > >>> semantics to some implementation-defined limit that is friendly for > >>mux'd > >>> http2 transport. > >>> > >>Thanks. > >> > >>Strictly speaking, RFC6455 allows an extension to give meaning to > >>WebSocket > >>frames, so merging / fragmenting frames breaks such extensions. > >>We discussed this problem in HyBi and many of us said "don't care". > > > >Yeah extensions except for compression have just not come into > >existence. > > > >So I also see it as don't care. I'm not even sure it's true since the > >intention during ws discussion was an intermediary can fragment frames > >same as how tcp packets may be fragmented. > > > >>In any case, an http/2 frame cannot be bigger than 2^24 (or 2^14 > >>without an > >>explicit permission), so I think we don't have to worry about DoS. > > > >... I don't see that. If I keep spamming 16MB frames even on one > >stream on a consumer link your latency goes to pieces and if something > >is doing multiple instances of it even a big pipe will feel pain. > > > >>> >I guess it can be done in parallel with http2 coming to an end > >>rather > >>> >than > >>> >> trying to block it, just by defining some new optional frame > >>types... > >>> > > >>> >I agree to define a ws-dedicated frame type and use it. > >>> > >>> Super... has anyone proposed how to map RFC6455 to http2 framing in > >>detail > >>> yet? > >>> > >>I think not. > >>I did list several ways at [1], but I deleted it from the next > > > >Alright I will go look at these. > > 5.2.1 is like pure tunneling, it's simple alright but it's bloated for > small frames. > > 5.2.2 has a needless flushing thing on top... in a real ws setup pieces of > data can arrive any old way they should be passed on as they come or > coalsced according to intermediary policy, I don't see the point. > > 5.3.3 headers + data per websocket frame... super inefficient > > Has it already been discussed to just merge http2 frame with ws frame? > > - use the headers scheme you defined to negotiate the connection + ws > protocol > > - There's an http2 frame type called like WSDATA > > - WSDATA's 8-bit flags field, is the ws flags [fin][rsv1-3][opcode] > > - WSDATA's payload, is the ws frame payload... the ws framing disappears > completely into the http2 framing. > > ... what problems does this create? > > -Andy > > >The discussion is moribund somebody should probably issue a 'stalking > >horse' since it's easier for people to jump in and tell you you're > >doing it wrong ^^ > > > >-Andy > > > >>version[2] > >>because HTTP/2 situation had changed. > >> > >>1: > >>http://tools.ietf.org/html/draft-hirano-httpbis-websocket-over-http2-00 > >>2: > >>http://tools.ietf.org/html/draft-hirano-httpbis-websocket-over-http2-01 > >> > >> > >>> > >>> -Andy > >>> > >>> > > >>> >On Fri, Nov 21, 2014 at 10:47 AM, Andy Green <andy@warmcat.com> > >>wrote: > >>> > > >>> >> > >>> >> > >>> >> On 21 November 2014 04:11:53 GMT+08:00, Robert Collins < > >>> >> robertc@robertcollins.net> wrote: > >>> >> >On 15 October 2014 00:00, Amos Jeffries <squid3@treenet.co.nz> > >>> >wrote: > >>> >> >> -----BEGIN PGP SIGNED MESSAGE----- > >>> >> >> Hash: SHA1 > >>> >> >> > >>> >> >> On 14/10/2014 11:01 p.m., Robert Collins wrote: > >>> >> >>> On 1 October 2014 23:37, Amos Jeffries wrote: > >>> >> >>> > >>> >> >>>>> All the implementor discussion I've seen during the > >>> >> >>>>>> HTTP/2 discussions has focused on how intermediaries want > >>to > >>> >> >>>>>> be scalable: and buffering is anti-scaling. So - is it a > >>> >> >>>>>> pragmatic concern, or do we expect DATA stream buffering > >to > >>> >> >>>>>> take place [outside of protocol gateways converting to > >>> >> >>>>>> HTTP/1.1 where non upload can require buffering - and note > >>> >> >>>>>> that such a gateway can't carry ws anyway unless its aware > >>of > >>> >> >>>>>> it, and if its aware of it, it can make sure it does not > >>> >> >>>>>> buffer]. > >>> >> >>>> > >>> >> >>>> > >>> >> >>>> I think the problem is not buffering in HTTP/2 per-se but > >the > >>> >> >>>> DATA frame (de-)aggregation that can happen if the frames > >are > >>> >> >>>> buffered by general network conditions (ie in TCP > >>bottlenecks). > >>> >> >>>> This would not be good for a 1:1 relationship between DATA > >>and > >>> >ws > >>> >> >>>> frames. > >>> >> >>>> > >>> >> >>>> Amos > >>> >> >>> > >>> >> >>> So hang on a second here. If we say that ws frames can't be > >>split > >>> >> >>> over multiple HTTP/2 frames that implies that we have to > >>buffer > >>> >> >>> them until there is enough in the window to transmit a > >>> >potentially > >>> >> >>> very large packet all at once. It also conflicts with RFC6455 > >>- > >>> >the > >>> >> >>> specific intent there is to not be a stream based system. > >>> >> >> > >>> >> >> If a ws frame *has* to be that long, not doing so would block > >>the > >>> >> >> entire HTTP/2 connection until all bytes of that frame were > >>> >delivered > >>> >> >> anyway. So you trade off buffering that single frame at the > >>> >sender, > >>> >> >> versus blocking all HTTP/2 traffic end-to-end. > >>> >> >> > >>> >> >> If the ws data is so critical to get transmitted fast why is > >>that > >>> >> >> single ws frame so large to begin with? surely it would be > >>> >> >transmitted > >>> >> >> faster as a sequence of WS + *WSDATA frames emited as the > >>payload > >>> >was > >>> >> >> available to send. > >>> >> > > >>> >> >I agree that its inconsistent which is why I don't think it > >>matters > >>> >> > >>> >> I am the author of libwebsockets, we are adding http2 support at > >>the > >>> >> moment. The basic http2 serving is done and works for http, but > >>> >we're all > >>> >> dressed up and nowhere to go in terms of treating websocket > >>> >connections as > >>> >> just another kind of http2, since the framing is "TBD". I am > >>sorry I > >>> >am a > >>> >> bit late to the party. > >>> >> > >>> >> I think you have to take the atomic large ws frame thing as a > >>genuine > >>> >> problem because http2 has the transmit credit concept. So even > >if > >>> >you > >>> >> buffered one ws frame, you can't sit there spewing as much http2 > >>DATA > >>> >frame > >>> >> as it needs to atomically encapsulate it, without sizing your > >>http2 > >>> >frame > >>> >> to suit the tx credit. > >>> >> > >>> >> But it's OK because the implementation can transparently fragment > >>the > >>> >ws > >>> >> data using the ws message semantics... I think there's no choice > >>but > >>> >to > >>> >> take that approach. > >>> >> > >>> >> Otherwise you get into being able to DoS even an http2 "big pipe > >>> >> aggregation" by just one mux element spewing an endless ws frame > >>and > >>> >> blocking every other mux'd connection... it cannot be right. > >>> >> > >>> >> >and mapping down to h2 frames as a sequence of octets would be > >>fine. > >>> >> >But you seem to both agree with my reasoning and disagree with > >my > >>> >> >conclusion. This is confusing. > >>> >> > > >>> >> >>> I was suggesting that we just treat the HTTP/2 stream like > >the > >>> >TCP > >>> >> >>> connection in RFC 6455 - the conversation from stream to > >>message > >>> >> >>> based semantics and so on can take place above that in the ws > >>> >> >>> implementation - and that we should still apply the > >>transmission > >>> >> >>> windows etc to ws streams. > >>> >> > >>> >> Yes ---^ this is how it has to be I think. > >>> >> > >>> >> >> If you do that you loose any and all benefits from HTTP/2 > >>frames. > >>> >> >> Everything from ws frame headers to data content becomes > >>> >semantically > >>> >> >> identical to the opaque payload of a DATA frame on an HTTP/2 > >>> >CONNECT > >>> >> >> request. I believe Yutaka is seeking to get away from that > >>> >situation > >>> >> >> where DATA frames may be split, joined or buffered at any > >>point. > >>> >> > > >>> >> >Sorry, I just don't follow that. We have a primitive which > >>appears > >>> >to > >>> >> >fit ws entirely, with the only caveat being that we haven't > >>defined > >>> >> >the mapping from the high level frames to the h2 primitives. If > >>the > >>> >> > >>> >> Yeah. > >>> >> > >>> >> >spec identifies how ws is negotiated and framed within h2, its > >>not > >>> >> >opaque at all. And ws implementations that support raw ws (which > >>> >> >they'll do for quite some time...) have to deal with tcp which > >>> >offers > >>> >> >no better semantics than this. > >>> >> > >>> >> Right now if I understood it the ws connections can still > >>negotiate > >>> >> themselves transparently inside http2 mux connections, using the > >>> >RFC6455 > >>> >> upgrade on their individual session ID, do the extra RTT and tx > >>data > >>> >> masking. > >>> >> > >>> >> Formalizing how to encapsulate the same thing in http2 doesn't > >buy > >>> >much > >>> >> above that... the benefit we can get is map the RFC6455 framing > >on > >>to > >>> >http2 > >>> >> native framing and get rid of the duplication simple > >encapsulation > >>> >has (for > >>> >> many small frames, it would be really painful overhead actually). > > > >>So > >>> >if we > >>> >> will do anything, it should indeed be define how to map RFC6455 > >>> >framing on > >>> >> http2 framing. > >>> >> > >>> >> I guess it can be done in parallel with http2 coming to an end > >>rather > >>> >than > >>> >> trying to block it, just by defining some new optional frame > >>types... > >>> >> > >>> >> -Andy > >>> >> > >>> >> >-Rob > >>> >> > >>> >> > >>> >> > >>> > >>> > >
- HTTP/2 and Websockets Robert Collins
- Re: HTTP/2 and Websockets Yutaka Hirano
- Re: HTTP/2 and Websockets Ilari Liusvaara
- Re: HTTP/2 and Websockets Yutaka Hirano
- Re: HTTP/2 and Websockets Greg Wilkins
- Re: HTTP/2 and Websockets Ilari Liusvaara
- Re: HTTP/2 and Websockets Robert Collins
- Re: HTTP/2 and Websockets Ilari Liusvaara
- Re: HTTP/2 and Websockets Yutaka Hirano
- Re: HTTP/2 and Websockets Yutaka Hirano
- Re: HTTP/2 and Websockets Amos Jeffries
- Re: HTTP/2 and Websockets Robert Collins
- Re: HTTP/2 and Websockets Yutaka Hirano
- Re: HTTP/2 and Websockets Amos Jeffries
- Re: HTTP/2 and Websockets Robert Collins
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Yutaka Hirano
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Yutaka Hirano
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Yutaka Hirano
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Yutaka Hirano
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Yutaka Hirano
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Robert Collins
- Re: HTTP/2 and Websockets Robert Collins
- Re: HTTP/2 and Websockets Yutaka Hirano
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Amos Jeffries
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Amos Jeffries
- Re: HTTP/2 and Websockets Jason Greene
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Jason Greene
- Re: HTTP/2 and Websockets Jason Greene
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Jason Greene
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Amos Jeffries
- Re: HTTP/2 and Websockets Robert Collins
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Yutaka Hirano
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Amos Jeffries
- Re: HTTP/2 and Websockets Yutaka Hirano
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Martin Thomson
- Re: HTTP/2 and Websockets Jason Greene
- Re: HTTP/2 and Websockets Martin Thomson
- Re: HTTP/2 and Websockets Roberto Peon
- Re: HTTP/2 and Websockets Willy Tarreau
- Re: HTTP/2 and Websockets Jason Greene
- Re: HTTP/2 and Websockets Jason Greene
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Yutaka Hirano
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Yutaka Hirano
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Yutaka Hirano
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Martin Thomson
- Re: HTTP/2 and Websockets Willy Tarreau
- Re: HTTP/2 and Websockets Amos Jeffries
- Re: HTTP/2 and Websockets Greg Wilkins
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Andy Green
- Re: HTTP/2 and Websockets Amos Jeffries
- Re: HTTP/2 and Websockets Roberto Peon
- Re: HTTP/2 and Websockets Yutaka Hirano
- Re: HTTP/2 and Websockets Yutaka Hirano
- Re: HTTP/2 and Websockets Martin Thomson
- Re: HTTP/2 and Websockets Roberto Peon
- Re: HTTP/2 and Websockets Brad Fitzpatrick
- Re: HTTP/2 and Websockets Roberto Peon
- Re: HTTP/2 and Websockets Glen Knowles
- Re: HTTP/2 and Websockets Roberto Peon
- Re: HTTP/2 and Websockets Wenbo Zhu