[
https://issues.apache.org/jira/browse/S4-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131397#comment-13131397
]
Karthik Kambatla commented on S4-15:
------------------------------------
This ties very well to the Netty initialization problem as well. Though the
netty-initialization can be solved in other ways, the order of creating
Listener and Emitter instances can solve the problem.
We want the NettyListener to be created first so that the NettyEmitter can
connect to it. Bruce had to move the connections part of the emitter to a
different thread to allow Listener initialization.
> Picking a communication protocol
> --------------------------------
>
> Key: S4-15
> URL: https://issues.apache.org/jira/browse/S4-15
> Project: Apache S4
> Issue Type: Improvement
> Reporter: Karthik Kambatla
> Priority: Minor
>
> Currently, the application (the associated module) require binding both the
> emitter and listener classes. Such an approach allows improper selections -
> e.g. UDPEmitter for Emitter and NettyListener for Listener.
> Instead, one should pick a communication protocol, the appropriate Emitter
> and Listener classes should be automatically picked.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
