e invoked directly via <code>peer_socket-&gt;get_executor()</code>, and any potential associated executor on these functions themselves is ignored. (This is the case simply because there was no internal-to-rest-of-Flow-IPC use case for acting otherwise; but it's conceivable to implement it later, albeit at the cost of some more processor cycles used.)</p>
<h3>Features of <code>boost::asio::async_read()</code> not provided here</h3>
<p >We have (consciously) made these concessions: ...see <a class="el" href=