[Cyberduck-trac] [Cyberduck] #927: Set queue / transfer item as "exclusive connection"

Cyberduck trac at trac.cyberduck.ch
Wed Oct 18 01:50:35 CEST 2006

#927: Set queue / transfer item as "exclusive connection"
 Reporter:  jamescat     |       Owner:  dkocher
     Type:  enhancement  |      Status:  new    
 Priority:  normal       |   Milestone:  2.7    
Component:  core         |     Version:  2.6.2  
 Severity:  normal       |    Keywords:         
 I would like to request a feature where certain files (well, transfers,
 since dirs count too) could be set as an "exclusive download" in the queue
 / transfers window.

 The idea is that it must wait till no other transfers are in progress, and
 then to disallow other queue items from starting until it has been
 completed. (Basically setting the max connections to 1 (one) universally
 instead of by host, as I believe it does now. -- But also unsetting this
 automatically when any such transfer has finished.)

 This way, if you have a massive file (e.g. ISO image) or hierarchy (e.g.
 the entire tree for a development project or web site perhaps), you could
 specify that it should have full use of your available bandwidth during
 its transfer.

 Of course, you can merely make sure that you don't add other items to the
 queue... Or manually switch your preference setting to 1 connection and
 reset it after you're done. -- But that's inconvenient if you want to
 download say 17 700MB ISO's in a row, or want to do this regularly. You'd
 have to go back and add each one when the previous one finished, or
 constantly be flipping your preference setting... instead of being able to
 add them all, mark them as "exclusive", and walk away.

 By allowing this option you do not risk having 5 of them complete 300 MB
 each (running concurrently) and then drop them if your connection
 "flutters" so that 1500MB was wasted on non-restartable servers (not
 common anymore, but "Yuck!" when you find them) -- but instead could have
 successfully downloaded 2 700MB ISO's and fail just 1 by having them all
 run consecutively instead of concurrently.

 But this "per transfer option" also allows for doing so just once, while
 having your default concurrency rate at a more reasonable level for the
 "normal"-style transfers that you do all the time.

 Okay, so it's not a "widely desired" feature, I'm sure. But it could be
 quite helpful to some people, such as myself who run into just such
 situations more often than I'd like. :)

Ticket URL: <http://trac.cyberduck.ch/ticket/927>
Cyberduck <http://cyberduck.ch>
FTP and SFTP Browser for Mac OS X.

More information about the Cyberduck-trac mailing list