mldonkey, a multi-networks file-sharing client - Patches: patch #2400, Horde-like pairing
You are not allowed to post comments on this tracker with your current authentication level.
patch #2400: Horde-like pairing
Submitter: | None | ||
Submitted: | Tue 02 Dec 2003 10:55:58 AM UTC | ||
Category: | Improved interfaces | Priority: | 3 - Low |
Status: | Postponed | Assigned to: | None |
Originator Email: | -email is unavailable- | Open/Closed: | Closed |
Mon 15 Mar 2004 07:59:02 AM UTC, comment #4: |
Anonymous |
Mon 08 Mar 2004 10:14:11 PM UTC, comment #3: real Horde looks quite different...
|
Anonymous |
Wed 03 Dec 2003 11:29:56 AM UTC, comment #2: BT try to estimate rate of clients. (bTRate.ml) It seems to classify quite well clients.
|
HighTime <HighTime> |
Tue 02 Dec 2003 01:18:49 PM UTC, comment #1: as expected from a late change, I introduced some bug (sign bug in rate computation)
|
Anonymous |
Tue 02 Dec 2003 10:55:58 AM UTC, original submission:
Give upload priority to fast sources (works better with dynamic upload management, patch #2238).
|
Anonymous |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 5 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2005-05-30 | spiralvoice | Reassign Item | From group mldonkey, a multi-networks file-sharing client, patch tracker | To group mldonkey, a multi-networks file-sharing client, task tracker | |
2005-01-03 | amorphous | Status | None | Postponed | |
2004-01-13 | alessandronip | Carbon-Copy | Removed alessandronip | - | |
2003-12-30 | alessandronip | Carbon-Copy | - | Added alessandronip | |
2003-12-02 | None | Attached File | - | Added horde_like2.patch, #2420 |
Powered by Savane 3.13-f8d8.
Corresponding source code
in the overnet-docu it's written that it "searches" for partners... so it probably requests a partner-reply from the other side...
so the point shouldn't be to behave like we have a partner, the point is to REQUEST a partner but I can't see from the discription that this patch would do that...
so maybe that should be the point to start with (to write or to document)
so long