Of all the engines for JVM/Android for HTTP Client...

# ktor

[Orhan Tozan]

Of all the engines for JVM/Android for HTTP Client, which one is recommended?: Apache, CIO, Jetty, OkHttp, HttpUrlConnection?

[e5l]

Hi @Orhan Tozan, for client or server?

[Orhan Tozan]

For client*

[e5l]

What version of android are you targeting?

[Orhan Tozan]

min21+, target 29

[e5l]

Android , OkHttp and CIO works fine. First 2 has several restrictions about post-get with body. In other cases you will not see the difference.

[gabin]

Android engine is fine

[Orhan Tozan]

My networking module is targeting jvm(), which will be used by the main android app, is it fine if I use CIO then instead?

[Orhan Tozan]

Reading that CIO is ktor's implementation, will this be the recommended engine in the future?

[e5l]

Yep. CIO engine has the same implementation on all platforms

[Dariusz Kuc]

just wondering, is CIO engine behaving similar to Spring WebClient in that it doesn’t block the threads or is it more of a Retrofit model where it is backed by some blocking threadpool?

[russhwolf]

Wait is CIO multiplatform? I thought it was just JVM. Or is that planned to change?

[Dominaezzz]

Planned to change.

[e5l]

@Dariusz Kuc, CIO is non-blocking(except domain name resolution)

[Dariusz Kuc]

awesome