I have no idea what you are talking about here. Thread locals always work. The value of the variable is scoped by the thread. What Bill is wanting is the ability to flush the variables associated with a thread in the scope of a thread pool. This is a different semantic that can be implemented as a map of thread locals accessed through the thread pool.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Jeff Haynie" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 16, 2003 10:52 AM Subject: RE: [JBoss-dev] ThreadPooling in JMX? Its broken > What happens in the case the executing thread doesn't know he's > executing on a thread pool thread - such as that another caller is > calling a method on an object via a thread pool? In this case, you > thread local variables wouldn't work -- in which case, thread locals are > pointless, no? ------------------------------------------------------- This SF.NET email is sponsored by: Thawte.com Understand how to protect your customers personal information by implementing SSL on your Apache Web Server. Click here to get our FREE Thawte Apache Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
