Clojurians Log v2

actually the use case we’re targeting here is chatty lambdas which fetch many small pieces of data from the server, so not a browser/CDN situation

Often Ring adapters will sit behind a load balancer or reverse proxy like nginx. These typically support HTTP/2 or even 3, and translate to HTTP/1.1 when forwarding the request to the adapter. In fact, last I checked, nginx only supported forwarding HTTP/1. Server Push won't be added to Ring, because support for it has been removed from browsers. It's effectively a dead end. I'm not aware of any other features of HTTP/2 or HTTP/3 that would require a Ring spec change, except as a way of optimising performance.

got it that all makes sense. Main thing I think we want is tcp multiplexing, so I’m not quite clear if downgrading via a reverse proxy is much of a performance win. Agree that maybe this doesn’t really affect ring semantics, but I guess we’d like to see http2 opt-in in the official ring-jetty-adapter

It depends on your setup, but for production use I use either a CDN or nginx for serving static resources, which represent the vast majority of data transfer. I'd certainly be open to adding HTTP/2 support to the official Ring adapter though. Only reason its not there yet is because I've had no reason/time to add it.

I know https://github.com/sunng87/ring-jetty9-adapter supports, curious how much community usage that has