[
https://issues.apache.org/jira/browse/THRIFT-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17430200#comment-17430200
]
Jens Geyer commented on THRIFT-5416:
------------------------------------
>From the pull request: bforbis commented on 6 Jun
{quote}
Yes, this would not work for anyone who is using non-void style RPC calls,
however considering that UDP is not the default protocol, I find it unlikely
this will actually cause any issues for users. Using UDP with thrift should be
considered an advanced option and someone who intentionally sets up their
client to use UDP should be responsible for understanding the tradeoffs between
UDP and TCP and know what they are getting into.
As for setting up a UDP server, I specifically don't have a use case for it in
perl so did not implement any server side code. In my example, Jaeger Agent is
already setup to be a thrift UDP server (presumably that means there is already
thrift UDP server support in golang, though I haven't looked closely at the
Jaeger codebase to see if they wrote their own custom thrift code).
Perhaps I could just leave some documentation in the source file about the use
cases for tcp vs udp.
{quote}
> Allow UDP Socket Client In Perl
> -------------------------------
>
> Key: THRIFT-5416
> URL: https://issues.apache.org/jira/browse/THRIFT-5416
> Project: Thrift
> Issue Type: Improvement
> Components: Perl - Library
> Reporter: Brian Forbis
> Priority: Minor
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The current Socket.pm module only allows for creating a TCP socket client.
> Some implementations that use Thrift (notably Jaeger Agent), use the UDP
> protocol.
> A quick solution to enabling Thrift over UDP is to allow the client to
> specify the protocol when creating the socket instance, otherwise have it
> default to using TCP.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
