Boost logo

Boost :

Subject: [boost] [RPC] Boost.Asio to write *concurrency ready* code
From: Niall Douglas (s_sourceforge_at_[hidden])
Date: 2013-08-27 13:41:39

On 27 Aug 2013 at 12:00, boost-request_at_[hidden] wrote:

> I am *not sure* if anyone else has made such discovery, anyway,
> comment is welcomed.

What you have discovered is well known I am afraid. Indeed, proposed
Boost.AFIO from this year's GSoC implements an asynchronous chainable
closure execution engine on ASIO, and you can read documentation on
how AFIO is equivalent to Google's and Microsoft's WG21 closure
execution engine proposals here:

Paul did up a great matrix mapping APIs from those engines to AFIO
equivalents at

If we get time before GSoC closes, we may just go ahead and implement
using AFIO as it would be incredibly trivial to do so. However, the
Boost community only voted closure execution support as third most
important - they ranked directory change monitoring as highest, so
that's what me and Paul are implementing now.

(FYI to those interested, we're going to deliver some *seriously*
performant directory monitoring. Testing of our direct kernel syscall
based implementation
suggests watching a 1 million file entry directory for changes will
work on Windows, albeit pegging a 3.5Ghz 4 core machine at 75-85% of
all CPUs.
Linux sadly lacks the syscalls to match Windows, but a 100,000 entry
directory may well work just fine)


Currently unemployed and looking for work.
Work Portfolio:

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