3 ms·
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...defeat
by 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 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.