[
https://issues.apache.org/jira/browse/DIRMINA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506933
]
Kenji Hollis commented on DIRMINA-341:
--------------------------------------
To make more sense, why not visualize it. Here's a proposal to an idea for a
change to the org.apache.mina.integration.spring.Binding class:
<bean class="org.apache.mina.integration.spring.Binding">
<property name="address">
<list>
127.0.0.1:2525
10.10.10.25:2525
10.10.10.25:2526
</list>
</property>
</bean>
Which will allow the Binding to bind to those three addresses. Then, you can
use getLocalAddress and the port to which the connection was made. It may make
more sense to attach it specifically to a different IoSession so the IoSession
only applies to the connected socket, and a context attached therein. But
either way would probably work for the first release of 2.0.0. I think a
context switch would make sense there, however, so different rules or
connection rules can be applied to different binding ports.
Say, for instance, someone wants to do a blacklist on 10.10.10.25:2526, but not
on 10.10.10.25:2525; this is why a context switch may make sense in this
regard. Just something to think about.
> 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.
