On 2010-04-19, at 19:42, Joshua Bell wrote: > That's a completely different issue. The lower level transport > protocol guarantees reliable delivery of certain types of messages - > packets are ack'd and resent if missed.
1. Are these messages actually being handled by that mechanism? 2. I have seen similar failure modes in downloads over TCP where the end-user software declined to cross reference the expected size of the file and the size of the file actually transferred and reported a complete transfer when it wasn't actually completed. Not only does the lower level transport have to guarantee delivery, the higher level has to notice whether that happened or not. Telling it how many objects to expect (size of the file) or transferring a terminating token (eg, the way zip puts the directory at the end of the archive... which is how I discovered this problem) is a common safeguard. _______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
