Is the response body read async, even with the OkH...
# ktord
dave08
10/21/2018, 12:25 PMIs the response body read async, even with the OkHttp engine (I'm currently interested in downloads) @orangy? How stable is CIO?
t
thevery
10/21/2018, 12:51 PMFor okhttp it is probably easier to check sources :)
d
dave08
10/21/2018, 12:54 PMKtor has byte channels that seem to be using Coroutines, the thing is whether that also needs a thread pool to run on, or is the implementation all async...
j
jw
10/21/2018, 1:39 PMOkHttp is all blocking I/O on its own pool
👍🏼 1
d
dave08
10/21/2018, 1:41 PMSo it's not possible to read the response body async... the docs are a bit misleading then:
Copy code
val readChannel = response.call.receive<ByteReadChannel>()
val inputStream = response.call.receive<InputStream>() Remember that InputStream API is synchronous!readChannelj
jw
10/21/2018, 1:43 PMI suspect the body is read on OkHttp's pool and sent over the channel to user code
j
jw
10/21/2018, 1:46 PMThat's for sending the request, not reading the response
d
dave08
10/21/2018, 1:48 PMOh,
OutgoingContentdave08
10/21/2018, 1:49 PMg
gildor
10/22/2018, 5:29 AMthat it’s asyncIt is async of course. Are you talking about syncronous/asyncronous or about blocking/non-blocking? Because Ktor uses syncronous blocking API of OkHttp (it doesn’t have any non-blocking one) that blocking but on own thread pool, but this API wrapped to asyncronous coroutines
d
dave08
10/22/2018, 6:24 AMThanks, I meant non-blocking, so even reading response content is done blocking? I'm not so familiar with Nio to know whether the fact they use it under the hood is also blocking. I knew for sure the request and initial response is blocking. @gildor
72 Views