On Tue, Apr 19, 2011 at 10:43 AM, Abhishek Kona <[email protected]> wrote: > 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,
Can you file an issue on github about that? > 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). They don't have to, no. > 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). You have to use the framed transport. > What kind of performance gains have you guys observed with using Netty as > the underlying transport layer. I don't know that we have any direct comparison benchmarks, but finagle is in general more performant than its competitors. -ryan
