
Hello Vicente,
2013/4/12 Vicente J. Botet Escriba
The project Boost.ThreadPool was developed taking in account the old Boost.Thread interface when the future library was not accepted in Boost yet. As far as I know the author (O. Kowalke) is working on an alternative design based on Boost.Context/Fibers instead of threads. IMO both approaches have a use depending on the application context.
your are referring to boost.task (former name was boost.threadpool)? yes I still working on it - as you know I was asked to move some of the functionality into separate libraries (-> boost.context, boost.fiber), which I finish soon. Boost.task already contains a threadpool while each worker-thread schedules fibers using boost.fiber in order to handle blocking tasks etc. Oliver