- From: Amos Jeffries <squid3@treenet.co.nz>
- Date: Tue, 27 Mar 2012 11:47:39 +1300
- To: <ietf-http-wg@w3.org>
On 26.03.2012 22:13, Ted Hardie wrote: > I'm seeing a bunch of messages that seem to be based on the > assumption > that after the creation of an HTTP 2.0 that all HTTP 1.x would > disappear in the transition to HTTP 2.0. I am not anticipating a > flag > day here, and I would guess that HTTP 1.1 would still be around for > any use cases that do not need features of any 2.0 proposal. Does > that make sense to others, or do we have a design constraint that all > use cases currently met by HTTP 1.X must also be met (with the same > security and performance properties) by 2.0? By my reading that is the chartered requirement anyway. If we do not meet or improve all scenarios already *in-use* within HTTP/1.x then the upgrade attempt will have failed. Why bother moving to or even creating a protocol that does not do what we need it to? IMHO, best not to do it with a flag-day, but the WG may disagree on that. AYJ
Received on Monday, 26 March 2012 22:48:07 UTC