We rely on server-sent events for streaming. Nearly all browsers are limited to 6 concurrent connections per server. HTTP/2 enables multiplexing, so this becomes a non-issue.
Ktor supports HTTP/2 under the Jetty, Netty, and Tomcat engines. Problem is, we use CIO (i.e., coroutines), and our architecture is partially based on the assumption that parallel jobs are cheap, so this is tricky to solve. To not switch, KTOR-2350 must be addressed.
We rely on server-sent events for streaming. Nearly all browsers are limited to 6 concurrent connections per server. HTTP/2 enables multiplexing, so this becomes a non-issue.
Ktor supports HTTP/2 under the Jetty, Netty, and Tomcat engines. Problem is, we use CIO (i.e., coroutines), and our architecture is partially based on the assumption that parallel jobs are cheap, so this is tricky to solve. To not switch, KTOR-2350 must be addressed.