Hi there,
On 9 Aug 2004, at 15:31, Howard Lewis Ship wrote:
In the dept. of general cleanups ... ThreadLocalStorage seemed like a good idea at the time, but with service-property:, ServicePropertyFactory and threaded/pooled services it doesn't seem to be such a good idea. I don't forsee myself ever using it and would like to remove it. thoughts?
I actually implemented something using the ThreadLocalStorage service just last week. I used it as a direct replacement to java.lang.ThreadLocal. Was this not its intention? In this particular situation, ThreadLocal was used to store context information about a particular request that could be picked up from anywhere in the call hierarchy. I know this sounds like hideous design, but it's not, I promise -- I'm over simplifying here!
Overall, I'm not too worried if you feel it should be removed -- I'm only really using it because it allows me to 'swap out' real ThreadLocalStorage for a fake one for my unit tests. I could either just use java.lang.ThreadLocal directly, or implement my own version of the service. I leave the call to you, but just wanted you to be aware that there was at least one person using it!
Cheers,
Paul -- Paul Russell [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
