coreycauble

@JimKnopf I agree 100% that would be the ideal situation. @RomanZ Would it not be possible for the seeder to service only those requests that would meet the goal of no duplication of chucks to its peers until a full distribution of the file is achieved. Then service the repeat requests? because in theory the client peers are should be requesting all of the chunks anyway, particularly when it is an initial seed. On to my question: I would like to know if during an initial seed the leaches do not share chunks. In the tests I have done chunks from multiple sources do not appear until they have finished downloading the entire file. It would be great if we could get a representation in the clients of what chunks are being moved much like standard bittorrent clients as it would vastly improve debugging.

How are you monitoring your peers?