[
https://issues.apache.org/jira/browse/THRIFT-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994862#comment-12994862
]
Chris Morgan commented on THRIFT-904:
-------------------------------------
Nagle is disabled in TSocket and TSocketServer for C# in trunk as of last week
to match c++ and java.
Is the frame transport more complex than the straight socket approach? Is the
difference that the framed approach buffers the data whereas the socket
approach sends it directly? I'm wondering if having nagle off for the simple
case and on for the more advanced cases that can buffer/group the send up is
the best approach.
> C# TSocket should disable nagle and linger
> ------------------------------------------
>
> Key: THRIFT-904
> URL: https://issues.apache.org/jira/browse/THRIFT-904
> Project: Thrift
> Issue Type: Bug
> Components: C# - Library
> Reporter: Jonathan Ellis
> Assignee: Alexey Biryukov
> Fix For: 0.6
>
> Attachments: thrift-904.patch, thrift-904.tests.patch
>
>
> Java sets
> socket_.setSoLinger(false, 0);
> socket_.setTcpNoDelay(true);
> C# should do the equivalent.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
