Ryan,
Thanks for the open source code.
I am unable to build finagle, (looks like it depends on twitter internal
repo's), any help on that will be appreciated,
A few questions if you don't mind:
* Do the server and client both have to use Netty Based Encoders and
Handlers for Thrift (I see both the implementations in the twitter
code).
* As thrift protocol's read a given number of bytes in a blocking
fashion , how does this implementation manage to buffer (or
accumulate) bytes from the Netty events ( is it thrift Protocol
specific, if so which one).
* What kind of performance gains have you guys observed with using
Netty as the underlying transport layer.
-Abhishek Kona
On 18/04/11 10:38 PM, Ryan King wrote:
On Fri, Apr 15, 2011 at 5:59 AM, Abhishek Kona<[email protected]> wrote:
Hi folks,
Has anyone used a Thrift server with Netty as the connection layer, have
heard some good things about it (apparently twitter is using it).
I have tried to creating a netty based thrift server by using the
TNettyTransport available athttps://github.com/cgbystrom/netty-tools
So any help / sample code in this regard is greatly welcome.
Also it would be nice to hear about other people(s) experience using thrift
and Netty.
The main problem I am trying to solve using Netty is increase the number of
connections (not physical) that can be made to the Thrift Server.
Our (Twitter's) implementation is open source:
https://github.com/twitter/finagle/tree/master/finagle-thrift
-ryan
