Quote:
Originally posted by Kaapeli without Keep-Alive and HTTP-pipelinig small chunks may have huge negative affect to the transfer rates. |
Correct. It makes no sense to swarm with small chunks without Keep-Alive support.
BearShare divides a file into chunks equal to 2.5% of the file size.
Using this method, along with the necessary Keep-Alive support, makes it EASY to add additional sources to the download (they just request different same-sized chunks).
You also don't have to make any funky estimates of the speed of the remote host in order to figure out how much to ask for (like LimeWire's original swarming implementation).
I believe LimeWire has switched to the fixed-chunk size scheme I described above.
Note "fixed chunk scheme" means that all chunks are equally sized (in BearShare's case, 2.5% of the file size).
"Variable chunk scheme" means that for a single file, the size of chunks requested from different hosts might be different.