[
https://issues.apache.org/jira/browse/S4-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133212#comment-13133212
]
kishore gopalakrishna commented on S4-15:
-----------------------------------------
This can be solved in the distributed mode by actually having the mode in the
task. The emitter can always chose the right emitter based on the listening
mode of the listener node.
In S4 as a service, we can actually support multiple protocols. And the stream
can specify the mode of transport and we chose appropriate protocol. This will
be very powerful because in general getting events into the system will use a
different protocol and once they are in s4 they will use a different protocol.
> Picking a communication protocol
> --------------------------------
>
> Key: S4-15
> URL: https://issues.apache.org/jira/browse/S4-15
> Project: Apache S4
> Issue Type: Improvement
> Affects Versions: 0.5
> Reporter: Karthik Kambatla
> Fix For: 0.5
>
>
> 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
