<br><div class="gmail_quote">On Wed, Mar 4, 2009 at 11:23 AM, Igor R <span dir="ltr">&lt;<a href="mailto:boost.lists@gmail.com">boost.lists@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">&gt; Asio or Boost::Threads simply ignore each other and nowhere in the docs<br>
&gt; of asio is stated smth about boost::threads, but as it seems asio socket<br>
&gt; when it waits for input is in such an interruption point (may be it uses<br>
&gt; boost::threads internally)<br>
<br>
</div>Are you sure asio launches threads, besides the ones you supplied for<br>
io_service::run()?<br>
<div></div></blockquote><div><br>No, that was not my point. If you use a socket from multiple threads
and read data from it, socket blocks waiting for input. My point was,
that this blocking wait is recognized by boost::thread lib as a valid
interruption point. And my suggestion would be to state in the docs of
Asio that synchronous wait operation is a valid interruption point for
boost::thread. Sorry for misleading words. Therefore interrupting the
thread should interrupt the synchronous wait.<br> 
<br></div></div><br>

