[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Download manager
From:       Shane Wright <me () shanewright ! co ! uk>
Date:       2002-05-06 15:04:21
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi

> Anyway, back to earth, stop/resume would be rather easy to add (FileCopyJob
> has suspend()/resume() already) ... but what's the point? I understand the
> usefulness of resuming a transfer that aborted (and some metainfo about the
> original URL would indeed be useful), but what's the point in temporarily
> pausing an existing transfer? Or do I misunderstand this Stop/Resume idea?

Stop/Resume is useful for letting the user manage their bandwidth; i.e. lots 
of downloads on, but wants to pause them to free up bandwidth for a quick 
Quake blat, or they find something they want to download quickly so they 
pause the others until the important file is done.

Speed limiting is also useful, as is setting the max # of concurrent 
transfers.

- -- 
Shane
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE81pt15DXg6dCMBrQRArWTAJ4h3Mth7K6jwT/s97Czq3/xgrd/8wCfWlzq
XZl0EUh9s51PPmUUdHOwppI=
=SvER
-----END PGP SIGNATURE-----


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]