You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Mark Webb (JIRA)" <ji...@apache.org> on 2007/10/04 01:29:50 UTC
[jira] Created: (DIRMINA-453) Multiple NioSocketAcceptors for one
java.nio.Selector
Multiple NioSocketAcceptors for one java.nio.Selector
-----------------------------------------------------
Key: DIRMINA-453
URL: https://issues.apache.org/jira/browse/DIRMINA-453
Project: MINA
Issue Type: New Feature
Components: Core
Affects Versions: 2.0.0-M1
Environment: All
Reporter: Mark Webb
Please see the discussion:
http://www.nabble.com/multiple-handlers-per-IoService-t4481513s16868.html#a12779214
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRMINA-453) Multiple IoServices for one
java.nio.Selector
Posted by "Mark Webb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRMINA-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Webb updated DIRMINA-453:
------------------------------
Description:
Please see the discussion:
http://www.nabble.com/multiple-handlers-per-IoService-t4481513s16868.html#a12779214
Based on discussions with Trustin, this is functionality that will be in the 2.0 release. It seems to be inefficient to create a new selector/thread for each IoService. This means that an application that is listening on 2 ports, would need two java.nio.Selectors, two Selector worker threads and each have a pool of workers.
Not only does this create much duplication, but more threads will be created than may be necessary.
was:
Please see the discussion:
http://www.nabble.com/multiple-handlers-per-IoService-t4481513s16868.html#a12779214
Summary: Multiple IoServices for one java.nio.Selector (was: Multiple NioSocketAcceptors for one java.nio.Selector)
> Multiple IoServices for one java.nio.Selector
> ---------------------------------------------
>
> Key: DIRMINA-453
> URL: https://issues.apache.org/jira/browse/DIRMINA-453
> Project: MINA
> Issue Type: New Feature
> Components: Core
> Affects Versions: 2.0.0-M1
> Environment: All
> Reporter: Mark Webb
>
> Please see the discussion:
> http://www.nabble.com/multiple-handlers-per-IoService-t4481513s16868.html#a12779214
> Based on discussions with Trustin, this is functionality that will be in the 2.0 release. It seems to be inefficient to create a new selector/thread for each IoService. This means that an application that is listening on 2 ports, would need two java.nio.Selectors, two Selector worker threads and each have a pool of workers.
> Not only does this create much duplication, but more threads will be created than may be necessary.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-453) Multiple IoServices for one
java.nio.Selector
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRMINA-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694109#action_12694109 ]
Emmanuel Lecharny commented on DIRMINA-453:
-------------------------------------------
I *think* we already have the capacity to use only one single selector for many sockets. No need to create new acceptors, just inject the ServerSocket into this NioAcceptor, and you are done.
> Multiple IoServices for one java.nio.Selector
> ---------------------------------------------
>
> Key: DIRMINA-453
> URL: https://issues.apache.org/jira/browse/DIRMINA-453
> Project: MINA
> Issue Type: New Feature
> Components: Core
> Affects Versions: 2.0.0-M1
> Environment: All
> Reporter: Mark Webb
> Fix For: 3.0.0-M1
>
>
> Please see the discussion:
> http://www.nabble.com/multiple-handlers-per-IoService-t4481513s16868.html#a12779214
> Based on discussions with Trustin, this is functionality that will be in the 2.0 release. It seems to be inefficient to create a new selector/thread for each IoService. This means that an application that is listening on 2 ports, would need two java.nio.Selectors, two Selector worker threads and each have a pool of workers.
> Not only does this create much duplication, but more threads will be created than may be necessary.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRMINA-453) Multiple IoServices for one
java.nio.Selector
Posted by "Julien Vermillard (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRMINA-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julien Vermillard updated DIRMINA-453:
--------------------------------------
Fix Version/s: 3.0.0-M1
> Multiple IoServices for one java.nio.Selector
> ---------------------------------------------
>
> Key: DIRMINA-453
> URL: https://issues.apache.org/jira/browse/DIRMINA-453
> Project: MINA
> Issue Type: New Feature
> Components: Core
> Affects Versions: 2.0.0-M1
> Environment: All
> Reporter: Mark Webb
> Fix For: 3.0.0-M1
>
>
> Please see the discussion:
> http://www.nabble.com/multiple-handlers-per-IoService-t4481513s16868.html#a12779214
> Based on discussions with Trustin, this is functionality that will be in the 2.0 release. It seems to be inefficient to create a new selector/thread for each IoService. This means that an application that is listening on 2 ports, would need two java.nio.Selectors, two Selector worker threads and each have a pool of workers.
> Not only does this create much duplication, but more threads will be created than may be necessary.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.