- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Tue, 13 Aug 2013 22:18:56 +0100
- To: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
- Cc: William Chan (ιζΊζ) <willchan@chromium.org>, Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
On 13 August 2013 22:06, Ilari Liusvaara <ilari.liusvaara@elisanet.fi> wrote: > I don't mean X -> HTTP/2.0 upgrade, but upgrading a stream from HTTP/2.0 > to something else. > > E.g. Full-blown websockets implementation (as opposed to potentially > simplified one built into HTTP/2.0). For the most part, that really isn't much different to what we've described for CONNECT. Upgrade implies something else, that is: I want to move from the current protocol (HTTP/2.0) to some other protocol (WS). That's non-trivial in a multiplexed protocol, even if HTTP/2.0 isn't really multiplexed in a fundamental way.
Received on Tuesday, 13 August 2013 21:19:23 UTC