- From: Henrik Nordström <henrik@henriknordstrom.net>
- Date: Thu, 01 Mar 2012 00:50:25 +0100
- To: Mike Belshe <mike@belshe.com>
- Cc: ietf-http-wg@w3.org
ons 2012-02-29 klockan 15:16 -0800 skrev Mike Belshe: > The problem with upgrade is that it costs a round trip of latency. Only if you are pipelining and then only on the second request, and pipelining on the first request is generally a bad idea anyway. So no. It's just means that the initial request (not it's response) is limited to HTTP/1.x wire format and that you can't pipeline if the protocol change means pipelined requests can not be properly parsed after the protocol change. And if HTTP/2.x preserve initial request-line structure compatibility with HTTP/1.x like it should then future requests to the same server should be able to assume the server is HTTP/2.x capable from start, until rejected, and you can even pipeline during the protocol upgrade if desired. Regards Henrik
Received on Wednesday, 29 February 2012 23:50:51 UTC