[
https://issues.apache.org/jira/browse/DIRMINA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506226
]
Kenji Hollis commented on DIRMINA-341:
--------------------------------------
When a message comes in in the message handler portion of the IO code, how do
you get the bound address for which the message was intended? Is this
something that's in the IoSession for the getLocalAddress()? If so, there's no
way to get the port that the connection was bound to is there? That would
probably make the job a little easier for people to determine which port a
connection was attached to.
I agree, using a single selector thread for the multiple bind addresses is a
good thing(tm).
What may also be a good idea is to create a connection context or a service
context that specifies the service space in which a connection has been
connected to. This way, the system can automatically "context switch" between
different configurations based on the connected port that an IoSession is
attached to. Something like an IoSessionContext? Just a thought.
> Allow binding multiple SocketAddresses per IoAcceptor.
> ------------------------------------------------------
>
> Key: DIRMINA-341
> URL: https://issues.apache.org/jira/browse/DIRMINA-341
> Project: MINA
> Issue Type: New Feature
> Components: Core
> Reporter: Trustin Lee
> Fix For: 2.0.0-M1
>
>
> 2.0-M1-SNAPSHOT allows only one SocketAddress to be bound per IoAcceptor.
> People want to bind the same protocol handler into more than one NICs with
> different port.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
