Re: [Boost-users] ASIO: Writing Composed Operations

Subject: Re: [Boost-users] ASIO: Writing Composed Operations
From: Cristian Morales Vega (cristian_at_[hidden])
Date: 2018-12-18 09:57:22

On Mon, 17 Dec 2018 at 23:00, Damian Jarek <damian.jarek93_at_[hidden]> wrote:
> A currently running handler is considered work, so you don't need the second guard, because before the handler is dispatched, it's the timer's responsibility to maintain the guard for ctx2. After it calls `ctx.get_executor().dispatch()`, it will reset the guard, but the context will not stop until the handler is executed and returns.

OK. And the problem with my example is that
my_executor::on_work_started() doesn't really count all the
outstanding work since things like
https://github.com/boostorg/asio/blob/a6008b6427ddfc3222f83c53030c34c802c53b59/include/boost/asio/detail/impl/scheduler.ipp#L295
are invisible to it. Makes sense.