> From: Henri Yandell [mailto:[EMAIL PROTECTED]] > > According to the README, ThreadContext contains utilities for > managing thread context variables. [no kidding :)].
:) > To be honest I'm not entirely sure I get it. It appears to be > a thread-registry with pluggable mechanism for managing > ThreadLocal-like variables. Pluggable so policies can be set, > I assume on pooling etc. I am forwarding this to Avalon Dev to see if I can get some answers from the author. > One major issue for me is that it is a framework, it has one > central class ThreadContext and it is expected that > developers will supply their own implementation of a > ThreadPolicy. I'm not sure if this is always necessary or if > in most cases it functions on its own, it seems to always be > necessary. > > While I like frameworks, I'm not in favour of them in a core > reusable jar like Commons.Lang. I don't think we should be > expecting users to be extending classes just to use the functionality. > > However this might be my feeling that I'm 'not getting it' talking. > > To see the code, check out jakarta-avalon-excalibur and goto: > > jakarta-avalon-excalibur/threadcontext/src/java/org/apache/exc > alibur/threadcontext > > Any views? > > Hen > > > -- > To unsubscribe, e-mail: > <mailto:commons-dev-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
