[boost] Re: [taar] Interest in an HTTP application library on Asio/Beast

HTTP/2 and HTTP/3 are out of scope for taar, by design. Beast is HTTP/1.1 only, and the expected deployment puts a reverse proxy or load balancer in front that terminates TLS and h2/h3. That's how we run it in production too. REST, JSON-RPC, MCP (Streamable HTTP), SSE and WebSocket all work fine over HTTP/1.1. It was on the roadmap but the reasoning wasn't written down, so I just added a design note: https://rjahanbakhshi.github.io/boost.taar/boost_taar/design.html#boost_taar... The handler and protocol layers don't care how the bytes arrive, so in theory, if an HTTP/2 transport shows up in Beast or Http later, the same handlers should run on it.