HttpResponseDecoder buffering data

"이희승 (Trustin Lee)" trustin at gmail.com
Thu Aug 26 01:49:41 EDT 2010


That sounds very inefficient.  I will address this issue in Netty 4.

On 08/03/2010 03:45 AM, halfempty wrote:
> 
> Thanks Trustin. Sorry it took so long for me to reply back.
> 
> Currently what I'm doing to get the behavior I want is to put a
> HttpResponseDecoder with a chunk size of 1 in the pipeline, followed by my
> own implementation extending SimpleChannelUpstreamHandler. My handler
> buffers the bytes until it has a full frame, which it then passes on to my
> other code. So I think the direct answer to your question is that it is
> transforming the chunks into my own object representing a frame.
> 
> Thanks!

-- 
what we call human nature in actuality is human habit
http://gleamynode.net/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 293 bytes
Desc: OpenPGP digital signature
Url : http://lists.jboss.org/pipermail/netty-users/attachments/20100826/07f1c081/attachment.bin 


More information about the netty-users mailing list