Mailing-List: contact dev-help@mina.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mina.apache.org
Message-ID: <167807740.1260237138110.JavaMail.jira@brutus>
Date: Tue, 8 Dec 2009 01:52:18 +0000 (UTC)
From: "chuanwen chen (JIRA)" <jira@apache.org>
To: dev@mina.apache.org
Subject: [jira] Commented: (DIRMINA-668) Modify the way we use IoProcessors
In-Reply-To: <214452464.1236556316193.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DIRMINA-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787249#action_12787249 ] 

chuanwen chen commented on DIRMINA-668:
---------------------------------------

Sorry, my mistake, it is 1.x in my hand

> Modify the way we use IoProcessors
> ----------------------------------
>
>                 Key: DIRMINA-668
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-668
>             Project: MINA
>          Issue Type: Improvement
>    Affects Versions: 2.0.0-M4
>            Reporter: Emmanuel Lecharny
>             Fix For: 3.0.0-M1
>
>
> In the current code base, when accepting new connections, we pick a processor and register the news connection within the internal selector. In other words, we have as many selectors as we have IoProcessors.
> This is a potential problem if some request cost a lot to be executed, as every requests waiting on this IoProcessor will be blocked.
> It would be way better to use a single selector which dispatches requests to an Executor, as we will always have available threads ready to process the requests (unless the pool is saturated, but then we have a bigger issue ...)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.