Quote:
Originally posted by David91
The thoroughness of your investigation is to be applauded but it does little more than demonstrate what I said in my earlier post. You are always likely to see sequential downloads of some sections of the file when grouped searches are stopped and restarted.
|
no kidding.
Quote:
Originally posted by David91
You will also see some packets resent when the internal verification at the receiving end shows that a corruption has occurred during sending. You may also see sending restarted and so duplicating different packets of data when the connection is interrupted for some other reason.
|
why can i download several gig with bearshare (which doesn't do overlap/check/redownload corrupted stuff) without any bad files, but ALMOST EVERY LIMEWIRE DOWNLOAD I OBSERVE DOES THIS REDOWNLOAD THING CONSTANTLY?
Quote:
Originally posted by David91
The only point of interest is your suggestion that this is a phenomenon particular to Limewire. I find this unlikely but, to be honest, I can't get excited enough about it to investigate.
|
the only reason i posted this here is that it is a phenomenon unique to limewire downloads. i don't see this kind of thing (repeated download of the same part of a file) from any other servent. get excited already.
Quote:
Originally posted by David91
While it is true that there may be a certain degree of redundancy in the traffic between two linked hosts, it is unlikely to represent a serious traffic management problem for the network as a whole. There are far more serious issues in the traffic management arena to resolve. All I will venture is that this is not a malfunction on the part of either Limewire or Bearshare. |
there should be NO redundant http downloads. all this is happening over TCP, which guarantees end-to-end packet health, which means it's NOT a network problem. it's an application problem. and again, bearshare and every other servent downloading from me DOES NOT exhibit this behavior, only limewire.
does limewire have the option to generate a similar activity log? specifically, does it log "i'm getting this chunk again because i smell corruption"?