Could you just open a ticket? I'll look at it then.
________________________________
Von: captncraig
Gesendet: 20.10.2014 21:40
An: dev@thrift.apache.org
Betreff: [GitHub] thrift pull request: Allowing use of buffered sockets in go
server
GitHub user captncraig opened a pull request:
https://github.com/apache/thrift/pull/249
Allowing use of buffered sockets in go server
There is currently no way in a go server to use buffered sockets. Failing
to do so decreases performance significantly in my tests.
I added an option on TServerSocket to set the buffer size to use. This will
default to 1024 bytes, but can be disabled if desired to get back to the
original behavior by setting BufferSize to 0.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/captncraig/thrift go-bufferedServer
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/thrift/pull/249.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #249
----
commit fdaf2ac1ce1b6d81da23ce5e89277b8c103523e9
Author: Craig Peterson <cpeter...@ancestry.com>
Date: 2014-10-20T19:12:52Z
allowing use of buffered sockets in go server
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
