I know believe that the heavyweight class I'm using is now thread-safe, so I was thinking that if there was a pool implementation that only created one instance (per key) and then would dispose it when it was never used again, I could swap in that pool implementation and do threadsafe testing without much code rewrite.
Is there such a trivial pool impl available, or does anybody have clever suggestions for how to do this? I figure I could manually go through and write a keyed pool impl to do this, but the trick is I do want it to eventually reap pool instances for keys that are never used... I just no longer want it to create multiple instances for an individual key.
Any tricks would be greatly appreciated.
-- Serge Knystautas President Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
