Hello, my server runs single io_service and asynchronosly accepts incoming connections (creating new sockets for each incoming connection).<br>Usage of connection happens in such ways:<br>     - calls to socket::async_write() from multiple threads (embraced to mutex) at any time<br>
     - handling socket::acync_read() (which runs within io_service&#39; thread as I understand the documentation)<br>     - single call to socket::shutdown() at any moment from some other thread<br>Previusly I used multiple of mutexes to cleanly wait for all current asynchronous read/write handlers: write function incremented &quot;writes&quot; variable which then was used on socket shutdown to wait the same amount of write handlers - but deadlock sometimes happend at moment of waiting write handlers. So I referred to socket::shutdown()&#39;s documentation which say &quot;Any asynchronous send, receive
            or connect operations will be cancelled immediately&quot; - and don&#39;t wait any asynchronous operations for now and everything seems to work fine for now (what scares me).<br><br>Is it safe to do so? How must I safely handle all currenlty running asynchronous read/write handlers?<br>
In case of boost.asio waits for all asynchronous operations to stop inside socket::shutdown/close so, then, if to call it within one of such operations - deadlock will (theoretically must) happen - so, socket::close/shutdown isn&#39;t safe?<br>
<br>Thank you.<br>