Hi Simon, Simon Meiklejohn <simon.meiklejohn@ipfx.com> wrote:
I see this requirement as a means of expressing constraints on a more general concept of execution context. Different implementations of execution context would carry out the post using different strategies
e.g. thread pools, new thread per post(), visitation of the execution context by a thread as work arrives (e.g. servicing execution in a shared system thread like the win32 message pump)
If the programmer could specify precursor code to execute before any posts are serviced, and also before and after each individual service that would be good.
The latest asio code in CVS includes the ability to hook and customise the dispatching of a handler, pretty much as we discussed during the review. There's a short discussion on it in the design section of the TR2 draft. Cheers, Chris