No, I mean when GetAvailableThreads returns 0 - is there a way to find
out how many tasks are waiting to access a thread.
For example, say my application gets bombarded with requests - each of
which is handled in its own ThreadPool thread. If the requests are
coming in faster than the ThreadPool delegate can execute, eventually
GetAvailableThreads will be 0. Once this happens, is there a way to
find out how many requests are waiting for a ThreadPool thread to
become available ?
> Hello Yofnik,
>
[quoted text clipped - 13 lines]
> "At times one remains faithful to a cause only because its opponents do not
> cease to be insipid." (c) Friedrich Nietzsche
William Stacey [MVP] - 24 Jul 2006 02:46 GMT
No direct way. You could wrap it and increment a counter in the
queueworkitem() and decrement in the callback helper wrapper.

Signature
William Stacey [MVP]
| No, I mean when GetAvailableThreads returns 0 - is there a way to find
| out how many tasks are waiting to access a thread.
[quoted text clipped - 23 lines]
| > "At times one remains faithful to a cause only because its opponents do not
| > cease to be insipid." (c) Friedrich Nietzsche