Thread pools of fixed size will be problematic

[Gregg Wonderly <ge...@cox.net>]

In a distributed application where you really don't know what a "thread" will do, you can't actually limit it's activity without creating a fairly large risk of circular wait for mesh like server interactions.  The ThreadPool class provides a few convenience services that are handy for the kind of work that the pool is targeted to do.  It would really not make sense to move that to a thread pool of a fixed size. 

Gregg Wonderly