Agree, that's why the protocol shift to Application layer, meaning you emulate what TCP does like how many packets and their sequence to order them at receiving layer for meaningful interpretation.
On Tue, Mar 1, 2016 at 11:01 AM, Mondain <mond...@gmail.com> wrote: > Ashish, just be aware that with UDP, some of your data may never arrive; > that's the nature of the protocol. > > Paul > > On Tue, Mar 1, 2016 at 1:48 PM Ashish <paliwalash...@gmail.com> wrote: > >> TCP handles fragmentation at its level, but for UDP you have to do it >> at application layer meaning UDP data has to carry message sequences >> and then you merge them at receiving end. Here you packets can come in >> different order do you got to keep them somewhere before complete >> message is constructed. >> >> >> >> On Tue, Mar 1, 2016 at 7:58 AM, tunca <atuncat...@gmail.com> wrote: >> > Our customer has strange requirement about merging multiple udp/TCP >> packages >> > to create a single message. >> > There is a well defined protocol that defines message boundaries. >> > The decoder is working good with TCP packages. It can create a single >> > message from multiple TCP packages. >> > However when a message is fragmented into multiple packages the do >> doDecode >> > method always gives the same ioBuffer. >> > I'll try 2.0.13 next day. >> > Thanks >> > >> > >> > >> > >> > -- >> > View this message in context: >> http://apache-mina.10907.n7.nabble.com/CumulativeProtocolDecoder-and-UDP-tp18927p50274.html >> > Sent from the Apache MINA Developer Forum mailing list archive at >> Nabble.com. >> >> >> >> -- >> thanks >> ashish >> >> Blog: http://www.ashishpaliwal.com/blog >> My Photo Galleries: http://www.pbase.com/ashishpaliwal >> -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
