You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mina.apache.org by "Jonathan Valliere (JIRA)" <ji...@apache.org> on 2019/05/24 14:07:00 UTC

[jira] [Resolved] (DIRMINA-577) Implement a Selector pool

     [ https://issues.apache.org/jira/browse/DIRMINA-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Valliere resolved DIRMINA-577.
---------------------------------------
    Resolution: Abandoned

> 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
>            Priority: Major
>             Fix For: 3.0.0-M3
>
>
> 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 was sent by Atlassian JIRA
(v7.6.3#76005)