SnapDive <(E-Mail Removed)> wrote in
news:(E-Mail Removed):
> I would like to instance 20 objects (not kidding about the number) on
> background threads and then issue asynchronous method calls to them.
> They do not need to send anything back to the caller. If one of the
> instances hangs then I would like to know.
So you have 20 calls at one time that are necessary for a single
process? Or are you trying to rewrite the thread pool in a custom
manner?
Spinning up threads and determining if there is an error is quite easy
in .NET with event handlers. And I see nothing particularly incidious
about 20 threads running in a .NET application.
The issue I see is if you are opening 20 threads and then leaving them
open for when you need to run processes, as this can be accomplished
through a thread pool without writing your own custom pool.
I guess the question is "what is the problem you are trying to solve?"
and not "How do I solve the problem THIS way?"
Peace and Grace,
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
Twitter: @gbworld
Blog:
http://gregorybeamer.spaces.live.com
*******************************************
| Think outside the box! |
*******************************************