- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Mon, 16 Oct 2017 15:15:31 +1100
- To: Andy Green <andy@warmcat.com>
- Cc: Patrick McManus <pmcmanus@mozilla.com>, hybi <hybi@ietf.org>, Cory Benfield <cory@lukasa.co.uk>, Patrick McManus <mcmanus@ducksong.com>, HTTP Working Group <ietf-http-wg@w3.org>
On Mon, Oct 16, 2017 at 3:06 PM, Andy Green <andy@warmcat.com> wrote: > What you are saying will save time I already assume is "for free" since it > happens during the time the HTML is fetched. Assuming that you need to some HTML, that will take a round trip, but that is concurrent with learning that the server supports websockets. After that, you should be able to CONNECT and send any frames at the same time: C: SETTINGS C: GET /index.html S: SETTINGS <-- I support :protocol S: 200 + DATA C: CONNECT + ws hs + DATA <-- client's first WS frames S: 200 + ws hs + DATA <-- server's first WS frames Still only two round trips. Were you concerned that the client needs to learn that the server supports websockets and not just :protocol?
Received on Monday, 16 October 2017 04:15:56 UTC