[mailto:boost-bounces@lists.boost.org] On Behalf Of Dmitry Ivankov

By the way, what about extending barrier so that it can use any functor not only waiting_threads == m_threshold? At least timed_barrier, which unblocks when (waiting_threads == m_threshold || time_since_first_wait > m_time_threshold), and maybe unblocks in destructor.

So it'll implement scenario: do the work in groups, i.e. not very often. That can be for example some time-expensive background cached work.

Thanks to the GP for the pointer to barrier. +1 for any functor from me anyway. The case I used was just an example. Barrier+functor would be higher-level, more obvious, and I'd think less prone to errors. Sohail