I'm curious, why are we still using an active worker thread instead of
letting the map clean up its dead references as they're encountered?
Wouldn't that fix the problem for 100% of users and simplify the code at
a slight performance cost?
Gili
Bob Lee wrote:
> This was just an update to the new API (MapMaker in place of
> ReferenceCache). I still need to address the issues w/ security contexts
> and inheritable thread locals.
>
> I think I can resolve the security reference by starting the thread in a
> doPriveleged() wrapper.
>
> I plan to use reflection to null out the inheritable thread locals in
> the new thread. This will work for 98% of users.
>
> 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
-~----------~----~----~----~------~----~------~--~---
