Return-Path: Delivered-To: apmail-directory-commits-archive@www.apache.org Received: (qmail 65448 invoked from network); 24 Dec 2005 01:24:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 24 Dec 2005 01:24:29 -0000 Received: (qmail 63396 invoked by uid 500); 24 Dec 2005 01:24:28 -0000 Delivered-To: apmail-directory-commits-archive@directory.apache.org Received: (qmail 63368 invoked by uid 500); 24 Dec 2005 01:24:28 -0000 Mailing-List: contact commits-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@directory.apache.org Delivered-To: mailing list commits@directory.apache.org Received: (qmail 63357 invoked by uid 99); 24 Dec 2005 01:24:27 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Dec 2005 17:24:27 -0800 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [209.237.227.194] (HELO minotaur.apache.org) (209.237.227.194) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 23 Dec 2005 17:24:27 -0800 Received: (qmail 65331 invoked by uid 65534); 24 Dec 2005 01:24:06 -0000 Message-ID: <20051224012406.65330.qmail@minotaur.apache.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r358891 - /directory/network/branches/0.8/xdocs/faq.fml Date: Sat, 24 Dec 2005 01:24:06 -0000 To: commits@directory.apache.org From: ersiner@apache.org X-Mailer: svnmailer-1.0.5 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Author: ersiner Date: Fri Dec 23 17:24:01 2005 New Revision: 358891 URL: http://svn.apache.org/viewcvs?rev=358891&view=rev Log: Updated thread safity part of the faq. Modified: directory/network/branches/0.8/xdocs/faq.fml Modified: directory/network/branches/0.8/xdocs/faq.fml URL: http://svn.apache.org/viewcvs/directory/network/branches/0.8/xdocs/faq.fml?rev=358891&r1=358890&r2=358891&view=diff ============================================================================== --- directory/network/branches/0.8/xdocs/faq.fml (original) +++ directory/network/branches/0.8/xdocs/faq.fml Fri Dec 23 17:24:01 2005 @@ -193,11 +193,15 @@

- You don't need to do because all events generated by MINA are - transmitted to your handlers in order, and the newer event is not - processed if the event handler method for the older event for - the same session didn't return yet because MINA uses leader-followers - thread pool by default. + It depends on your implementation. If you access the resource + which is shared across multiple sessions, you have to make it + thread-safe. If the resource is not shared at all and accessed + by only one session (e.g. storing context information as a session + attribute), then you don't need to make it thread-safe. It is + because all events generated by MINA are transmitted to your + handler in order, and the newer event is not processed if the + event handler method for the older event for the same session didn't + return yet because MINA uses leader-followers thread pool by default.