Not usually one to get behind speculation, but if one were to provide an educated guess, what does everyone think about the timeline of switchover from 1.1 to 2.0? 1 year? 5 years?
Personally I think we'll see a few big players jump in and then we'll see a domino effect as all the big servers complete their implementations (Apache, NGINX, Tomcat etc).
Of course HTTP/1.1 systems are going to be around for a loooong time...
My take is that browser support will be very fast, because of evergreen browsers.
I'm also guessing a majority of the top 500 sites will support it pretty quickly (on the order of a year or two). Everything else, will be a long tail of a decade or more.
Edit: Just wanted to add that, I think the better goal is "majority of traffic using HTTP/2" - that's probably 5 years because the majority of traffic probably comes down to the top 500 sites.
> Not usually one to get behind speculation, but if one were to provide an educated guess, what does everyone think about the timeline of switchover from 1.1 to 2.0? 1 year? 5 years?
Try never.
Too much embedded devices out there which 1. won't get updated, 2. doesn't have enough storage for a crypto-stack and 3. doesn't have the computational power to process a crypto-stack should it even be updated to have one.
Internet-standards are published, approved and then stays forever. You will realistically need to support all versions until "the end of time", or at least the end of the internet as we know it.
Well, in 2003 (14 years after the release of HTTP 1.1), Twitter considered it acceptable to remove HTTP 1.0 from their API access (You can still access the website itself fine over 1.0).
I expect to see 1.0, 1.1 and 2.0 continue to live on basically forever.
Of course, the interesting question will be how fast will the majority of users, and servers, be running 2.0?
Just to reinforce it, HTTP/2 is not a replacement for HTTP/1.1. It's an optimization for a few very important use cases, but it does not support most of the different ways HTTP is used everywhere.
Even for the cases it optimizes, one's recommended to verify if there's really any performance enhancement after deploying it, because there are several variables that could make it worse.
Months. Traditionally a change like this saw little enthusiasm or interest, and had a very slow uptake, because it didn't add value until all of the players changed. Now, however, browsers iterate so quickly that already there is HTTP/2 support on the majority of user desktops. If you run a Go or node.js or various other technology websites, even if you "self-host" HTTP, you likely (and should) have it behind nginx or Apache or HAProxy, and all of those are quickly implementing HTTP/2 (or more correctly changing the existing SPDY functionality to the final spec. And for those who wonder, a HTTP/1.1 Go app sitting behind a HTTP/2 proxy still delivers HTTP/2 benefits to the end user). Cloudflare had SPDY support over two years ago, so I expect they'll see very quick support.
Of course, and you addressed this, this doesn't mean that HTTP/1.1 disappears. Heck, my web properties still see HTTP/1.0 requests, almost a decade after HTTP/1.1. But that is a very small minority.
Like IPv6, HTTP/2 is a broken standard that doesn't solve any problems.
The problem with the Web isn't a lack of out-of-order requests, the problem with the Web are those horrible ever-present Javascript frameworks.
(Likewise, the problem with IPv4 isn't a lack of address space, the problem with IPv4 is a lack of a standard and simple way for managing VPNs and tunnels. I don't want my lightbulbs to be connected to the global Internet. What I _do_ want is a way to tunnel remotely and securely into my home's LAN and control the lightbulbs from the inside.)
[+] [-] wwarren|11 years ago|reply
Personally I think we'll see a few big players jump in and then we'll see a domino effect as all the big servers complete their implementations (Apache, NGINX, Tomcat etc).
Of course HTTP/1.1 systems are going to be around for a loooong time...
[+] [-] atonse|11 years ago|reply
I'm also guessing a majority of the top 500 sites will support it pretty quickly (on the order of a year or two). Everything else, will be a long tail of a decade or more.
Edit: Just wanted to add that, I think the better goal is "majority of traffic using HTTP/2" - that's probably 5 years because the majority of traffic probably comes down to the top 500 sites.
[+] [-] josteink|11 years ago|reply
Try never.
Too much embedded devices out there which 1. won't get updated, 2. doesn't have enough storage for a crypto-stack and 3. doesn't have the computational power to process a crypto-stack should it even be updated to have one.
Internet-standards are published, approved and then stays forever. You will realistically need to support all versions until "the end of time", or at least the end of the internet as we know it.
[+] [-] CJefferson|11 years ago|reply
I expect to see 1.0, 1.1 and 2.0 continue to live on basically forever.
Of course, the interesting question will be how fast will the majority of users, and servers, be running 2.0?
[+] [-] marcosdumay|11 years ago|reply
Even for the cases it optimizes, one's recommended to verify if there's really any performance enhancement after deploying it, because there are several variables that could make it worse.
[+] [-] mrottenkolber|11 years ago|reply
[+] [-] unknown|11 years ago|reply
[deleted]
[+] [-] ForHackernews|11 years ago|reply
[+] [-] engendered|11 years ago|reply
Of course, and you addressed this, this doesn't mean that HTTP/1.1 disappears. Heck, my web properties still see HTTP/1.0 requests, almost a decade after HTTP/1.1. But that is a very small minority.
[+] [-] otabdeveloper1|11 years ago|reply
Never.
Like IPv6, HTTP/2 is a broken standard that doesn't solve any problems.
The problem with the Web isn't a lack of out-of-order requests, the problem with the Web are those horrible ever-present Javascript frameworks.
(Likewise, the problem with IPv4 isn't a lack of address space, the problem with IPv4 is a lack of a standard and simple way for managing VPNs and tunnels. I don't want my lightbulbs to be connected to the global Internet. What I _do_ want is a way to tunnel remotely and securely into my home's LAN and control the lightbulbs from the inside.)
[+] [-] sctb|11 years ago|reply
[+] [-] unknown|11 years ago|reply
[deleted]
[+] [-] harkyns_castle|11 years ago|reply
[+] [-] dragonwriter|11 years ago|reply
[+] [-] halflings|11 years ago|reply
[1] http://www.infoworld.com/article/2612478/html5/berners-lee-a...