Boost logo

Boost :

From: Christopher Kohlhoff (chris_at_[hidden])
Date: 2006-08-14 22:25:00

Hi Simon,

Simon Meiklejohn <simon.meiklejohn_at_[hidden]> 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.


Boost list run by bdawes at, gregod at, cpdaniel at, john at