Opened 10 years ago
Last modified 10 years ago
#8522 new Bug report
Uploads are added to queue a few at a time
|Reported by:||matteo sisti sette||Owned by:|
|Component version:||Operating system type:||Linux|
|Operating system version:|
Steps to reproduce:
- navigate on the client side to a folder with a lot of files
- select all of them
- upload them
- all the files should be added to the queue immediately
- only a few are added to the queue, then after a while a few more are added, etc
I guess this is by design, but it is a completely wrong design that has no reason to be like this, and has huge drawbacks and no one single advantage.
I understand why _downloads_ are added to the queue like this (though an option should be provided to queue _all_ files for download before starting to download them, if one wants to, because there are a number of situation when one needs to have a complete queue). But there is NO reason at all for uploads to work like this.
Here's an obvious case of a problem this generates:
- there is some network issue that interrupts the upload, or anything that forces you to restart filezilla
=> After restarting filezilla, the queue is remembered, but the files that were going to be added to the queue are not. So you are left with a partial queue that you can resume but you have absolutely no way to figure out which are the files that need to be re-added to the queue.
This is made worst by a bunch of other bugs that make filezilla go completely berserk and uncapable of recovering at the slightest network problem, so you are forced to restart it very, very often, facing this issue. However this issue is an issue of its own and must be fixed regardless of the other ones that make it worse (i.e. even if you were never forced to restart filezilla without a reason, because you can always have a good external reason to have to restart it, and also because the behavior is plain wrong in the first place).
Change History (1)
comment:1 by , 10 years ago
|Priority:||critical → high|