Hi everyone ( hello <@U017TSBJ2C9> :slightly_smili...

# ktor

[Anthony Legay]

Hi everyone ( hello @Aleksei Tirman [JB] 🙂 ), I was just wondering, do we have any news regarding HTTP/2 support for CIO engine ? ( https://youtrack.jetbrains.com/issue/KTOR-2350 ) as the issue does not seem really active.
We're using OkHttp for quite some time on our backends but we thought giving CIO another chance ( the "fully async coroutine-based" promise is appealing! ). Should we honestly expect improvements on this in the near future or it's worth turning to Jetty for example, or even stick with OkHttp. I saw some article recommending CIO for backend services doing mainly calls to other API (which is exactly our case, many, many parallel calls to other external services).
Thanks in advance for any advice ! (also no "pressure" in the question 😄 just out of curiosity so we can make the right call.)

[simon.vergauwen]

Hi Anthony,
Did you see the comment on the YT issue? It's a quite big time investment to bring CIO on par with the other engines, without a clear promise that it will perform significantly better.

I.e. OkHttp is used by many companies, SDKS, etc. Same for Apache5 which is another great option for the JVM (if you don't need web sockets). All of these should be very efficient parallel calls to external services.

We'd love to invest more time and love into the CIO engine but we need to prioritise more urgent issues and features first.

[Anthony Legay]

Great ! I'm sorry I think I missed this part in the comments 🫣 my bad.
But fine by me, totally understandable given the current landscape. We'll stick to OkHttp. Thanks for your answer !