[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Mldonkey-bugs] [bugs #3932] Enhancement request: chunk availability ran

From: anonymous
Subject: [Mldonkey-bugs] [bugs #3932] Enhancement request: chunk availability ranking
Date: Sun, 05 Dec 2004 17:44:30 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041007 Galeon/1.3.17 (Debian package 1.3.17-2)

This mail is an automated notification from the bugs tracker
 of the project: mldonkey, a multi-networks file-sharing client.

[bugs #3932] Latest Modifications:

Changes by: Anonymous user
                dim 05.12.2004 at 17:32

------------------ Additional Follow-up Comments ----------------------------
As far as I know, mldonkey already does that.

[bugs #3932] Full Item Snapshot:

URL: <>
Project: mldonkey, a multi-networks file-sharing client
Submitted by: 0
On: mar 10.06.2003 at 05:26

Category:  Core
Severity:  5 - Average
Item Group:  Feature request
Resolution:  None
Privacy:  Public
Assigned to:  None
Status:  Open
Release:  2.5.3
Release:  2.5-3
Platform Version:  Mac OS X Jaguar
Binaries Origin:  None
CPU type:  None

Summary:  Enhancement request: chunk availability ranking

Original Submission:  A great enhancement for not so common files would be a 
ranking of chunks based upon their availability. Rare chunks of a file should 
be downloaded immediatelly upon becoming available. This would presumably 
greatly increase overall availability of chunks and therefore of complete files.

It is VERY annoying to see, that almost all connected clients show the same 
availability pattern so my client is going to assimilate this pattern, too. 
When there is a client making available those chunks that the others havent, it 
is discouraging to see, that my client first sucks the commonly available 
chunks first, often loosing the rare one again.

For follow-up: address@hidden

Follow-up Comments

Date: dim 05.12.2004 at 17:32       By: 0 <None>
As far as I know, mldonkey already does that.

Date: mar 24.02.2004 at 20:33       By: spiralvoice <spiralvoice>
Please check if this bug still is in current CVS version.
You should a tarball of current CVS in files section of
this project:

For detailed info, follow this link:

  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]