W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2012

Re: Review: http://www.ietf.org/id/draft-mbelshe-httpbis-spdy-00.txt

From: Henrik Nordström <henrik@henriknordstrom.net>
Date: Thu, 01 Mar 2012 00:50:25 +0100
Message-ID: <1330559425.24673.149.camel@home.hno.se>
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

Received on Wednesday, 29 February 2012 23:50:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:00 UTC