Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 67986 invoked from network); 17 Dec 2009 19:18:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Dec 2009 19:18:01 -0000 Received: (qmail 78632 invoked by uid 500); 17 Dec 2009 19:17:57 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 78594 invoked by uid 500); 17 Dec 2009 19:17:57 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 78583 invoked by uid 99); 17 Dec 2009 19:17:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Dec 2009 19:17:57 +0000 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=RCVD_IN_BL_SPAMCOP_NET,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of iamake@gmail.com designates 209.85.210.203 as permitted sender) Received: from [209.85.210.203] (HELO mail-yx0-f203.google.com) (209.85.210.203) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Dec 2009 19:17:48 +0000 Received: by yxe41 with SMTP id 41so7096213yxe.30 for ; Thu, 17 Dec 2009 11:17:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language; bh=dfPX5rTDcvEyGoy4uk+F8Q54ksYZw6mTTnYJOlz0v3k=; b=Hb6QhocjfXEq0x4VlNEacM3h6MIyAt3QqgVQUS9AnLwHw8pkwLyU9XyuETEn7Mpa3m Ru6koRq1zmIxCEnKhJxroezk7OFoV0Bp4DhlKdB8Ou5WvfEdC99l0MwM7zMz36XSf8Ai BU76rsmYO1/lOI5ZtvzT8r/B/vch8Noo45JK8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; b=St44qS9vFG8XfurXSv2WdYu32rMpYN6QMVrwPzKjnEsCaGoQtj8ICP2mNmqNlc16Ra YkXJwnT1BBc01+VCj4XcVyfmDKKsKD6wvCpL6lVivXADXehe9dXWx42cY/DSN+k4i//W 1QyYWybHe8r7MX9T4kgDvn2e1S5XxazHLnZZs= Received: by 10.100.19.32 with SMTP id 32mr4594610ans.80.1261077446010; Thu, 17 Dec 2009 11:17:26 -0800 (PST) Received: from akenotebook (ppp-124-120-177-206.revip2.asianet.co.th [124.120.177.206]) by mx.google.com with ESMTPS id 20sm833703ywh.17.2009.12.17.11.17.23 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 17 Dec 2009 11:17:25 -0800 (PST) From: "Ake Tangkananond" To: Subject: Tomcat thread model Date: Fri, 18 Dec 2009 02:17:17 +0700 Message-ID: <00ef01ca7f4d$8ff8d860$afea8920$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acp/TYvqsUG0CjfgTZGjoWvYptex+g== Content-Language: en-us X-Virus-Checked: Checked by ClamAV on apache.org Hello, I am finding a way to keep a variable in a request scope. I feel it is cumbersome to put that into request variable and pass it through multiple objects. So, I think I will make it accessible through a static class variable. I wonder if I can put it into a static ThreadLocal variable in a class? To rephrase the question: Though the thread pooling is possible, and one thread may serve multiple requests, can it be guaranteed that each thread will serve only a single request at the same time? If the answer is "yes", does this apply to all Java Servlet implementation ? Regards, Ake --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org