Re: [Boost-users] boost::asio blocking socket read with timeout with multiple threads

This argues for a separate io_context for use by that thread.

The arrangement of the io_services in the backend in that hypothetical design wouldn't really matter as everything would be done synchronously by that backend worker thread anyway. So it may as well be io_service per pipe (I've no idea whether there are inefficiencies either way, but I don't think it would make any difference to the way it behaved).