Object Encoder and Decoder Query

[Frederic Bregier]

Hi,

The decoder should. If you look at the code, the encoder first puts the
length of the
object so that the decoder can take care of it when it receives the packets
so that it makes the assembly correctly (like FrameDecoder).

But for the encoder, what do you mean by packet fragmentation?
If you mean the tcp/ip fragmentation, it is not at the level of netty
(tcp/ip
is under the wood) as a sender. But it is at the decoder part (as I wrote,
the decoder take care of the multiple packets from tcp/ip stack).

If you mean fragmentation of an object, it is at your level
(splitting a big object into several smaller objects), so before Netty,
but then you have to take care too after the decoder since you will
receive several objects and not only one.

Does this answer your question?
Frederic


manish_iitg wrote:
> 
> Does object encoder and decoder also take of packet fragmentation and
> assembly issue.
> 


-----
Hardware/Software Architect
-- 
View this message in context: http://n2.nabble.com/Object-Encoder-and-Decoder-Query-tp2012986p2016222.html
Sent from the Netty User Group mailing list archive at Nabble.com.