So, is using 'ThreadSafe' components as singletons that retain state between any given release() and subsequent lookup() a bad idea? I do this a lot. just wondering . . .
As long as you can guarantee that the state is not corrupted by multiple threads accessing the component simultaneously then you should be OK.
If you cannot make that guarantee, then you will run into concurrency problems.
-- "You know the world is going crazy when the best rapper is a white guy, the best golfer is a black guy, The Swiss hold the America's Cup, France is accusing the US of arrogance, and Germany doesn't want to go to war. And the 3 most powerful men in America are named 'Bush', 'Dick', and 'Colon' (sic)".
-----Chris Rock
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
