View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000412aMuleTransferpublic2005-05-06 03:152005-05-09 01:06
Reportertuxlover 
Assigned To 
PrioritynormalSeverityfeatureReproducibilityalways
StatusclosedResolutionopen 
PlatformOSOS Version
Product Version2.0.0 
Target VersionFixed in Version 
Summary0000412: download chunks with lowest availability first
DescriptionHi,
amule (and any other mule/donkey client) should download try to download chunks of a file that have the lowest availability first.
If the client has any influence in what part of a file it downloads when, it would be smartest to try to download the parts that have the lowest probability to be available later on, which are the ones with the lowest availability. amule already seems to have an availability measure about the single parts of a file (as can be seen in the colour display in the download queue window).

So when I get connected to another donkey/mule user, and am downloading a file with exactly 2 chunks, and the first chunk has a low availability (i.e., not a lot of other clients have that chunk) and the second chunk has a high availability (i.e., more clients have this chunk than the first), amule should decide to dowload the first chunk rather than the second.

I think this would keep the common situation from happening that I can download say 80% of a file but can't get the remaining 20% of it. It would also lead to a much better network situation.
Now that I'm thinking about it it seems so strange that this isn't implemented in the protocol by default. It doesn't seem to at least, the way all these mules/donkeys behave... compared to bittorrent.
TagsNo tags attached.
Fixed in Revision
Operating System
Attached Files

- Relationships

-  Notes
(0000960)
Kry (manager)
2005-05-09 01:06

That's actually how it works :)

- Issue History
Date Modified Username Field Change
2005-05-06 03:15 tuxlover New Issue
2005-05-09 01:06 Kry Status new => closed
2005-05-09 01:06 Kry Note Added: 0000960


Copyright © 2000 - 2025 MantisBT Team
Powered by Mantis Bugtracker