search

Nethravathitcs / unitt

Automatically exported from code.google.com/p/unitt
0 stars 0 forks source link

When a header comes at the end of a fragment, subsequent fragments are not assembled correctly #41

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
When receiving many messages I have seen cases where the message header would 
appear at the end of a fragment.  When this happens, the next time 
handleMessageData: gets called, it appends the new data to the fragment without 
taking into consideration the current fragment length.  This causes the header 
to be truncated from the message when it recursively calls handleMessageData 
with subset of the data fragment.

I've made this work by calculating a message offset that gets factored in when 
computing the subdata range.

Original issue reported on code.google.com by art.jacobson on 29 Feb 2012 at 8:59

Attachments:

GoogleCodeExporter commented 8 years ago 
Great find! I will take a look at this this week and get the code updated. 
Thank you!

Original comment by joshuadmorris@gmail.com on 1 Mar 2012 at 3:38

GoogleCodeExporter commented 8 years ago 
This is fixed in the 1.0.0-RC build now available.

Original comment by joshuadmorris@gmail.com on 26 Apr 2012 at 3:56