FrameDecoder Problem

[Tom Cheung]

Just discovered that, when FrameDecoder can return an Object,
FrameDecoder.decode will be called again immediately. And if the
FrameDecoder return a null, FrameDecoder.decode will be called one more
time, and if this time is also null, FrameDecoder.decode will not be called
again until there is new incoming buffer.
Thanks.


Tom Cheung wrote:
> 
> My case:
> Every messageReceived will carry several Object that I need to return,
> however the current design of FrameDecoder only support to return a single
> Object, should I return an ArrayList instead? Any potential problem if I
> do so? Thanks.
> 

-- 
View this message in context: http://n2.nabble.com/FrameDecoder-Problem-tp2160761p2160788.html
Sent from the Netty User Group mailing list archive at Nabble.com.