Adrian Crum wrote: > One of the things to keep in mind during these discussions is the > forthcoming ExecutionContext - a part of the security redesign. Instead > of passing a delegator around the framework, the current delegator is > assigned to the current thread and a static method exists to retrieve it > at any point in the execution path. > > I should have that code committed sometime late this week, or this > weekend at the latest. Even though the new security design is disabled, > the ExecutionContext can still be used. In fact, we can use it to start > fixing issues like the ones described here.
Global statics, even per-thread, can be very bad. Consider something stored into the cache, then referenced from another thread. What is the correct delegator? Does your branch remove all delegator instance variables and method parameters?
