No, you have it right, Johnathan. It's just that the way that Nonblocking/HsHa server work, they don't really use the supplied transport for anything except the last little bit of the pipeline prior to method invocation. Those two servers in particular are *implicitly* framed-transport-only.
On Sat, Nov 13, 2010 at 9:11 AM, Jonathan Ellis <[email protected]> wrote: > On Fri, Nov 12, 2010 at 5:56 PM, Bryan Duxbury <[email protected]> wrote: > > THsHaServer neither supports nor would benefit from TFastFramedTransport. > In > > fact, Both nonblocking and HsHa servers are pretty good already when it > > comes to interacting with the server-side per-request transport, so it's > > unnecessary. (There is an opportunity to make those servers reuse their > > buffers, but I haven't had a chance to make those changes yet.) > > I thought reusing its buffers was the whole point of > TFastFramedTransport. Are there other differences from TFramedT? > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of Riptano, the source for professional Cassandra support > http://riptano.com >
