#10801 closed Feature request (rejected)
After action queue completion feature request/return
| Reported by: | Jason | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | FileZilla Client |
| Keywords: | after action queue disconnect | Cc: | |
| Component version: | Operating system type: | Windows | |
| Operating system version: | win 7 |
Description
I use the disconnect from server option seen in this screenshot, http://i.imgur.com/p6pPS6q.jpg , when downloading files. That way I can start the download and walk away. Then when it's finished it will disconnect but not close the application. Then later I can check and make sure I have no failed transfers. If so I can restart them easily from that tab.
The latest version of filezilla has removed this option and stays connected after your queue has completed unless you choose to close the app when done. Then you lose your failed transfer tab data.
Can you please put this option back into that menu? I use this on both windows and Linux.
Change History (2)
comment:1 by , 9 years ago
| Resolution: | → rejected |
|---|---|
| Status: | new → closed |
comment:2 by , 9 years ago
That's not the only thing that defines a good feature in a piece of software. If it causes harm or not. Closing the connection as an alternative to closing the program completely is a good option to have.
Same as reboot and shutdown. Two complimentary options. Same as close the connection or close the program.
There's no harm done in keeping the connection open. Modern servers can easily handle tens of thousands of idle connections.