Is this still true in an environment that can be configured with fixed thread pools such as servlet containers and such? I was under the impression that the Map used was keyed off the thread ID and that was fixed. Plus I also thought they were all weak references.
I could see some possibility of issues if your thread pools shrink and grow, but as long as the references are traversable and self contained not bound to any long lived object, the weak references in the map should work as expected, correct? -bp On Sep 30, 2008, at 4:59 PM, Bob Lee wrote: > Are you sure you actually want thread local scope? It's very prone > to memory leaks. > > Bob > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-guice?hl=en -~----------~----~----~----~------~----~------~--~---
