[
https://issues.apache.org/jira/browse/S4-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591823#comment-13591823
]
Karthik Kambatla commented on S4-45:
------------------------------------
On S4-15, Matthieu suggested we don't have a configuration mechanism just yet.
My understanding was S4 would use s4-comm.properties file to configure this. Is
that approach still valid? If yes, I can go ahead and add the code to configure
it. Otherwise, I am not sure what is a good way to go about it.
If we have to go round about to add UDP support, I see the following options:
# If we think UDP is not worth supporting, I think we need to make a conscious
decision and close this JIRA out as "Won't Fix".
# If we think we might want to support UDP in the future but not as an
immediate priority, we should probably get the implementation in now and add
the configurability later? Just to make sure the work to port/refactor doesn't
go to a waste only to be done again later.
Either way, the committers should probably make a decision here.
> 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
>
> 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
