William, I'm not sure. I haven't been following the development branch, and don't know exactly how to access it. I called this class a function queue based on what I saw of the currently released boost::thread::thread_pool which was merely a collection of various threads that provided a grouped join. I needed to be abstracted from the thread itself. Thus, thread was not a good choice in the class's name.
eric "William E. Kempf" <[EMAIL PROTECTED]> wrote in message news:3666.167.16.75.51.1037032721.squirrel@;frodo.kempf-ville.com... > > Eric Woodruff said: > > Is there any interest in a threaded function queue? I ran into a problem > > where I needed to asynchronously run methods but I didn't want to (or > > actually couldn't easlily) maintain threads to run them in. So I created > > a function queue where I could control the number of threads that were > > used to execute the (Boost.Function) functions. There is a lot of room > > for customization like specifying policies for controlling how/if the > > processing thread collection can grow. > > Unless I'm not understanding precisely what you mean, it sounds like your > talking about a "thread_pool", as implemented in the thread_development > branch. Could you compare contrast what you have in mind with what's > available there? > > -- > William E. Kempf > > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost > _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
