4 ms·

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 cha

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.

theallan 12y ago
> Apache [...] are quickly implementing HTTP/2 Do you have a link to any development Apache are doing on HTTP/2? I asked about it in the previous HTTP/2 thread but there wasn't any replies and I haven't been able to find any myself. I know there is mod_spdy but that appears to be abandoned now [1]. [1] https://svn.apache.org/viewvc/httpd/mod_spdy/trunk/ https://svn.apache.org/viewvc/httpd/mod_spdy/trunk/
- engendered 12y ago
  You know, I actually can't find anything and may have incorrectly included Apache in the "keeping up" category. The whole Apache ecosystem almost seems...defeatist now. Google donated mod_spdy to the Apache foundation and it doesn't look like it has been touched since -- given that HTTP/2 is a derivative of SPDY, the existence of that module should make it a "relatively" (relative being, well, relative) simple change, but you're right that they don't seem to be on it.
  - jimjag 12y ago
    Actually, moving from SPDY to HTTP/2 isn't any easier than going from HTTP/1.1 to HTTP/2. Google's mod_spdy was nice, but required lots of core code changes, so it was more a proof of concept. And with SPDY changing so much, wasting time on development makes little sense and, considering that SPDY (having served its purpose) is now dead, some would say that it was wise not jumping on the bandwagon quickly. But Apache is hardly alone is having a "wait and see" attitude towards HTTP/2; both HAproxy and Varnish see HTTP/2 as a solution for the wrong problem.
cypher543 12y ago
Brad Fitzpatrick is actively working on HTTP/2 support for the Go standard library: https://github.com/bradfitz/http2 https://github.com/bradfitz/http2
jimjag 12y ago
The change will be due not to any real "success" or benefits associated with the protocol itself, but by major players, such as Google, forcing it through. They didn't spend all that time and money steamrolling HTTP/2 not to coerce the rest of the web to use it. Even so, the work done by some of the HTTP/2 authors is to be widely commended!

theallan 12y ago

> Apache [...] are quickly implementing HTTP/2 Do you have a link to any development Apache are doing on HTTP/2? I asked about it in the previous HTTP/2 thread but there wasn't any replies and I haven't been able to find any myself. I know there is mod_spdy but that appears to be abandoned now [1]. [1] https://svn.apache.org/viewvc/httpd/mod_spdy/trunk/ https://svn.apache.org/viewvc/httpd/mod_spdy/trunk/

engendered 12y ago
You know, I actually can't find anything and may have incorrectly included Apache in the "keeping up" category. The whole Apache ecosystem almost seems...defeatist now. Google donated mod_spdy to the Apache foundation and it doesn't look like it has been touched since -- given that HTTP/2 is a derivative of SPDY, the existence of that module should make it a "relatively" (relative being, well, relative) simple change, but you're right that they don't seem to be on it.
- jimjag 12y ago
  Actually, moving from SPDY to HTTP/2 isn't any easier than going from HTTP/1.1 to HTTP/2. Google's mod_spdy was nice, but required lots of core code changes, so it was more a proof of concept. And with SPDY changing so much, wasting time on development makes little sense and, considering that SPDY (having served its purpose) is now dead, some would say that it was wise not jumping on the bandwagon quickly. But Apache is hardly alone is having a "wait and see" attitude towards HTTP/2; both HAproxy and Varnish see HTTP/2 as a solution for the wrong problem.

cypher543 12y ago

Brad Fitzpatrick is actively working on HTTP/2 support for the Go standard library: https://github.com/bradfitz/http2 https://github.com/bradfitz/http2

jimjag 12y ago

The change will be due not to any real "success" or benefits associated with the protocol itself, but by major players, such as Google, forcing it through. They didn't spend all that time and money steamrolling HTTP/2 not to coerce the rest of the web to use it. Even so, the work done by some of the HTTP/2 authors is to be widely commended!