Hey, Thanks for the quick replies. Surely this isn't due to fragmentation? Wouldn't fragmentation come down to multiple reads per network packet being sent? Which would be fine, but all the messages that are being sent fit within a single tcp/ip packet and are being received as a single packet.
>>A message is not a "packet". You can have several messages in one "packet" or >>several "packets" for one message. I have one message per packet, and it is received as one packet also.. When I view Wireshark it clearly shows a time gap between the two receives and the fact the tcp/ip packet isn't full. This isn't a problem with it being incomplete, its a problem with it being over complete. >From reading the documentation I got the feeling that you have to cope with the received data not being complete and not that you have too much information. Best Regards, Mark Wallsgrove 2009/11/13 Mikhail Gerdov <[email protected]>: > Nature of TCP/IP lead to the fact that MINA can not guaranty that > every Send call will result to exactly one Read call. > There are ways to fight it by providing custom Decoder to handle > fragmentation. > Please read this: > http://mina.apache.org/handling-packet-fragementation.html > and look at CumulativeProtocolDecoder examples. > > > > On Fri, Nov 13, 2009 at 1:12 PM, Mark Wallsgrove > <[email protected]> wrote: >> Mina > > > > -- > Best regards, > Mikhail Gerdov mailto:[email protected] > -- Best Regards, Mark Wallsgrove
