> I'd like to go further: HTTP/2 is the present not just for content serving, but could be for APIs. Very true. The talk around around server push has suffered

> I'd like to go further: HTTP/2 is the present not just for content serving, but could be for APIs. Very true. The talk around around server push has suffered a bit from tunnel-vision, only taking browser-media delivery into account, making it look like a browser feature only. HTTP2 + server push can actually make GraphQL less relevant, same way that there hasn't been talk around supporting websockets in it (it just doesn't look necessary anymore). But for all this to happen, server push needs to become cacheable. And I really hope that the cache digests rfc takes off and gets more implementations.