9 ms·
I don't see why it'd be ordered for blocks received If I remember correctly, a node with a full file will send out the blocks in parallel, so leechers should r
by setr 7y ago
I don't see why it'd be ordered for blocks received
If I remember correctly, a node with a full file will send out the blocks in parallel, so leechers should receive blocks effectively in random order
The only reason for some machines having only the start versus the end would be implementation-wise, where maybe you see the want list ordered, and the seeder responds by only shipping the first n blocks it reads in the want list
If the seeder responds with random ordering, you'd avoid the problem of all leechers all having the same blocks