[
https://issues.apache.org/jira/browse/S4-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591827#comment-13591827
]
Matthieu Morel commented on S4-45:
----------------------------------
We did have a configuration mechanism for switching between transports.
However, we also refactored the way we configured applications, and in order to
handle app-specific events, the listener implementation can only be loaded in
the AppModule, i.e. through a app-aware classloader. And currently the listener
is hardcoded in that module to TCPListener.
There are certainly various means to enable configurability, but currently I'd
rather postpone that to a later release (>0.6).
> UDP should use Netty
> --------------------
>
> Key: S4-45
> URL: https://issues.apache.org/jira/browse/S4-45
> Project: Apache S4
> Issue Type: Improvement
> Affects Versions: 0.5.0
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Attachments: s4-45.patch
>
>
> UDPEmitter and UDPListener use our own implementation suffering from the
> following issues -
> 1. All send() calls are essentially serialized
> 2. If the listener thread is interrupted, it doesn't restart listening.
> Using Netty will solve the above-mentioned issues while making the code more
> maintainable as both UDP and TCP would then be using Netty.
> Comments or suggestions?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
