4 ms·
> 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
by 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 agoYou 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 agoActually, 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.