31 Jan
2011
31 Jan
'11
12:30 p.m.
It doesn't do that. It's smart enough to see that it's in a given strand which may be blocked so it moves on to the next available scheduled handler. I do it all the time and I haven't seen it be the bottleneck for anything I've developed with Boost.Asio even in the early days and leading up to especially now.
Give it a shot and then measure to identify which part of the solution is causing you problems.
Wow, you're right! Strands clearly do more than they appear to do. Thanks.