Yes, when you sendBlocking, your loops should wait...
# coroutinesd
dave08
05/08/2018, 11:45 AMYes, when you sendBlocking, your loops should wait until the processingPool can take the next request, so that thread will be blocked. On the processing coroutine side, it should spread the work to the processingPool (but I think you have to launch as many of them as you need to actually work in parallel... and as one consumes a request, the other one will try to consume the next one and they'll be spread evenly, like in the fan out link I referred to, but in your case, you don't need all that code, you could just use what I wrote before.. but I didn't do it exactly, you might have to look up a few things...)