Content ChannelBuffer Factory for HTTP Codec?

[Wade Poziombka]

You guys are doing great work. We are very keen to use Netty in our product. 
We've done a lot of testing of the various async frameworks and netty has
come out on top.  I was delighted to see the HTTP codec recently added as
that is of primary interest along with a few other protocols such as MLLP.  

We have some special needs as we integrate with some native components that
have a preexisting buffering mechanism (chains of buffers from pools in form
of native (shared memory) heap).

I do not want to use these buffers for all IO (but it would be ideal if the
HTTP content could be populated into these buffers without first buffering
the entire message then copying.  

It seems that if there were some mechanism for me to supply a ChannelBuffer
to the Codec when decoding the content portion of the message that I might
be able to achieve the desired affect.  

What I want to avoid is buffering the entire content of a request into
ChannelBuffer(s) and then have to copy it to other buffers, especially given
that these might be large (megabytes).

Any thoughts on this idea, or perhaps I'm missing a way to achieve this
already?
-- 
View this message in context: http://n2.nabble.com/Content-ChannelBuffer-Factory-for-HTTP-Codec--tp1607490p1607490.html
Sent from the Netty User Group mailing list archive at Nabble.com.