[
https://issues.apache.org/jira/browse/DIRMINA-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRMINA-453.
---------------------------------------
Resolution: Fixed
It's a long time we can bind more than one socket to a single acceptor, thus to
more than one selector. Now, we don't support the association of more than one
IoService to a single selector.
We won't do that in 2.0 anyway. This is opened for discussion in 3.0
> 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: 2.0.8
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
