Stover, Michael wrote:
> Good point. I think Klas specifically wants to know the thread numbers go
> from 1...N, however. I think it's not unreasonable to supply both.
>
By supplying our own ThreadGroup objects, we can have the ThreadGroup
name the threads properly--according to whatever standards we deem
useful.
Avalon's thread pooling code does this so that we know what pool the
thread came from, and which thread number it is.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
