8 May
2011
8 May
'11
1:06 p.m.
it's in /libs/asio/example/http/server4/coroutine.hpp and basically works with one huge switch-case construct.
I suspect that the problem has nothing to do with coroutines, since the two former contexts worked well and every context is independent from the others (they don't share data). The third one is not invoked BECAUSE the handler (which is scheduled after the last call to Context::asyncReadFromSocketIntoQueue) is not called, even if it's been scheduled for execution. So my question, actually, has nothing to do with coroutines (that part has been checked by me and, I suspect that it's not coroutine's fault (although it could be).