[
https://issues.apache.org/jira/browse/S4-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131686#comment-13131686
]
Leo Neumeyer commented on S4-15:
--------------------------------
Makes sense, I think, how would you do this? I wouldn't put anything in the
properties file because protocol will not change often. One way would be to
have a protocol interface. The only downside is that it is an interface on top
of two interfaces and just adds indirection. Since the protocol will not change
often, can we just validate at startup and exit with an error instead?
A related issue we discussed in the past is that we may want to configure
streams with isReliable (for example true: TCP, false: UDP) This would require
binding the isReliable value to a specific protocol implementation. One option
would be to implement a provides method in Module
(http://code.google.com/p/google-guice/wiki/ProvidesMethods). On the other
hand, we may want to wait to do this until we run some performance benchmarks
to see if there is a significant speed gain by using UDP vs TCP.
> 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
>
> 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
