Hi all, I was amazed about the huge interest in my threadpool lib in the last week. :-) Currently, it looks like there's a strong demand for having a thread pool included in boost. Anthony would like to add futures and a pool to boost::thread. I think this is a very good idea for two reasons. First, any boost thread pool should be based on boost::thread. This means platform independence for free. It does not make much sense to separate the libs because the threadpool part is small and requires the boost::thread binaries anyway. Second, we don't need a boost project setup for my lib. I guess it's much easier to integrate with boost::threads than to prepare a stand-alone library. Please let me know your opinions. Regards, Philipp On 10/31/07, Dean Michael Berris <mikhailberis@gmail.com> wrote:
On 10/31/07, Alex Ott <alexott@gmail.com> wrote:
Hello Michael
I had wrote this question to Phillip several days ago, so i know this asnwer ;-) After improvements in documentations, he plans to send it to review
Great! Thanks. :-)
At any rate, I think I'll contact him about helping with the documentation. It might also be a good idea if I take my further questions about thread pool with him directly.
Thanks again!
-- Dean Michael C. Berris Software Engineer, Friendster, Inc. [http://cplusplus-soup.blogspot.com/] [mikhailberis@gmail.com] [+63 928 7291459] [+1 408 4049523] _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost