Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 48730 invoked from network); 19 Jun 2002 19:19:40 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 19 Jun 2002 19:19:40 -0000 Received: (qmail 17143 invoked by uid 97); 19 Jun 2002 19:19:48 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 17106 invoked by uid 97); 19 Jun 2002 19:19:47 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 17094 invoked by uid 98); 19 Jun 2002 19:19:47 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) From: Ola Berg To: commons-dev@jakarta.apache.org Reply-To: Ola Berg MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit User-Agent: Tripnet Webmail (IMP/PHP) Sender: ola.berg@arkitema.se Subject: [lang] proposal: ThreadContext Message-Id: Date: Wed, 19 Jun 2002 21:19:38 +0200 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N OK, the script-kiddie with the bad ideas is back, this time with a proposal for lang: When doing servlets you have the app-context, the session-context and the request-context, where you can put variables (or context attributes as they are called). What about a ThreadContext where you can put variables that belongs to a certain thread? Wouldn\'t that make writing thread safe things easier? Object o = ThreadContext.getAttribute( \"fooBar\"): /O -------------------- ola.berg@arkitema.se 0733 - 99 99 17 -- To unsubscribe, e-mail: For additional commands, e-mail: