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.)
On Fri, Nov 12, 2010 at 2:50 PM, Ryan King <[email protected]> wrote: > We're trying to test TFastFramedTransport with a project, but we're > either misunderstanding something. > > We're trying to use it with THsHaServer, but ran into a few problems: > > * THsHaServer requrires a TFramedTransport.Factory, but > TFastFramedTransport.Factory isn't a subclass of that. Seems wrong, > no? > * also, since TFastFramedTransport.Factory doesn't memoize the > transport, we create a new object for each request and its therefore > at least as resource intensive as the alternative > > So yeah, I hope we're just missing something. Otherwise this > combination appears to be broken. > > -ryan >
