directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ersi...@apache.org
Subject svn commit: r358891 - /directory/network/branches/0.8/xdocs/faq.fml
Date Sat, 24 Dec 2005 01:24:06 GMT
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 @@
       </question>
       <answer>
         <p>
-          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.
         </p>
       </answer>
     </faq>



Mime
View raw message