so sktor-client-cio was buggy, okHttp works better...
# ktor
so sktor-client-cio was buggy, okHttp works better, except now apparently my application never leaves the main coroutine scope at the end
Hi, @Nikky. The
engine is experimental, but we put maximum effort to make it perform better.
Please report any problems that you find. I'll be really appreciated.
I just saw a thread somewhere here on slack, that okhttp has a pool of non daemon threads for IO which keep your application running for 60secs after the last connection terminates. If this is the case for you, you probably do leave the coroutineScope but your app still won't quit. Supposedly okhttp has a thread to make it's threads daemons
i did not figure out how to configure that and just used the apache engine