You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2008/11/21 19:29:44 UTC
[jira] Updated: (DIRMINA-577) Implement a Selector pool
[ https://issues.apache.org/jira/browse/DIRMINA-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRMINA-577:
--------------------------------------
Fix Version/s: (was: 2.0.0-M4)
3.0.0-M1
Postponed
> Implement a Selector pool
> --------------------------
>
> Key: DIRMINA-577
> URL: https://issues.apache.org/jira/browse/DIRMINA-577
> Project: MINA
> Issue Type: Improvement
> Affects Versions: 2.0.0-M1
> Reporter: Emmanuel Lecharny
> Fix For: 3.0.0-M1
>
>
> There is an interesting post from Jean-François Arcand : http://weblogs.java.net/blog/jfarcand/archive/2006/07/tricks_and_tips_4.html
> where he explains that we may use more than one single Selector to manage the incoming and outgoing events.
> Separating OP_READ, OP_WRITE and OP_ACCEPT selectors may lead to some improvement, depending on which kind of server you want to build.
> It seems interesting to implement these ideas in MINA.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.