Bug 63461 - Maximum number of open connections per server
Summary: Maximum number of open connections per server
Status: RESOLVED DUPLICATE of bug 57248
Alias: None
Product: kget
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-30 14:00 UTC by Damir Perisa
Modified: 2005-09-20 15:35 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Damir Perisa 2003-08-30 14:00:06 UTC
Version:           v0.8.3 (using KDE 3.1.3)
Installed from:    compiled sources
Compiler:          gcc version 3.3
OS:          Linux (i686) release 2.4.22

what about a limit of open connections per server?

often if you try to download more than one file from a slow server (research station with a ISDN modem :-) all your other transfers are on hold, because you have set "max open connections"=1 to not start all at the same time (starting more than 1 file from a slow server causes disconnections --- on the server-side)

-> asuming you have a fast connection and you want to download these things from different servers:

- knoppix-$version.iso (710MB)	at 91kb/s	1file
- something else (160MB)	at 72kb/s	39 files
- something else (..)		at 30kb/s	12 files
- research-data (19MB)		at 1,2kb/s	180 files

if you have your research data transfer started and set the limit of max connections to 1 (to not start all 180 transfers from the slow server), then all your other stuff your connection can handle easily are on hold and waiting the slow things to transfer ... starting things by hand one per one needs very anoying watching of transfers --- you cannot do other things while watching one file to be done and then start the next by hand
Comment 1 Urs Wolfer 2005-09-20 15:35:02 UTC

*** This bug has been marked as a duplicate of 57248 ***