[
https://issues.apache.org/jira/browse/S4-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433507#comment-13433507
]
Karthik Kambatla commented on S4-15:
------------------------------------
Should we go ahead and do this?
- I think it should be straight-forward to implement Leo's suggestion of
combining emitter/listener into a single protocol.
- We should be able to address Kishore's suggestion of supporting multiple
protocols also through the combined comm-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.0
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Fix For: 0.6
>
>
> 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
