Hi :) Trustin Lee wrote:
DemuxingProtocolCodecFactory cannot pass uninterpreted ByteBuffer because it cannot determine where the unknown message starts and ends. You have to add a MessageDecoder which writes the unknown part of the ByteBuffer to ProtocolDecoderOutput, then you can handle it in the next codec filter or handler.
this part describes exactly the point, where I'm confused. If the ProtocolDecoderOutput of the previous filter will be used (read in) in the next codec filter as part of the normal ByteBuffer too, all questions are answered. In older mails I've understood this part in an other way. I thought, that the ProtocolDecoderOutput would be directed to the IoSession without passing the rest of the filter chain. Did I understood here something false?
Best Regards Michael
