- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Thu, 17 Jul 2014 16:35:37 +0000
- To: Martin Thomson <martin.thomson@gmail.com>
- cc: Yutaka Hirano <yhirano@google.com>, Kari Hurtta <hurtta-ietf@elmme-mailer.org>, HTTPBIS working group mailing list <ietf-http-wg@w3.org>
In message <CABkgnnWey=iHxJO9AwOWa146-Cu1g8HJ-yXT8McXyo3W8aXgqw@mail.gmail.com> , Martin Thomson writes: >On 16 July 2014 23:24, Yutaka Hirano <yhirano@google.com> wrote: >> Then we need only client => server SETTINGS frame with WS_CPABABLE. >The only problem there is the added delay. A client can't open a >websocket in the first flight. So since this seems to be the standard reply to pretty much everything else, why doesn't it just negotiate WS with TLS (or Update:) to begin with ? Why the detour over HTTP/2 ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Received on Thursday, 17 July 2014 21:53:36 UTC