You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a user is not viewing via ftp browser window, but is engaging in FTP transfers via the "activity" window, if a user Stops the transfer, it does what it says. That is, it only Stops it, not diconnect if required.
Can Cyberduck add a button to Disconnect from particular transfer, not just stop them ?
As I believe, correct me if i'm wrong, but when you stop a transfer, connection is still up as stated in the documentation
"Interrupt
You can interrupt a transfer using the Stop toolbar button."
This feature could be useful, for example, if transfers are needing only to be active (ftp browser can be disconnected, while transfers continue) as there would be no point maintaing a idle connection to a ftp server unless actively using it.
The text was updated successfully, but these errors were encountered:
If you choose to open a new connection for file transfers (the file transfer appears in the Transfers window), then its connection is independant of the browser session and closed when the transfer has finished. If you choose to the browser connection for file transfers, the connection to the server is closed when you disconnect from the server or close the browser window.
If a user is not viewing via ftp browser window, but is engaging in FTP transfers via the "activity" window, if a user Stops the transfer, it does what it says. That is, it only Stops it, not diconnect if required.
Can Cyberduck add a button to Disconnect from particular transfer, not just stop them ?
As I believe, correct me if i'm wrong, but when you stop a transfer, connection is still up as stated in the documentation
"Interrupt
You can interrupt a transfer using the Stop toolbar button."
This feature could be useful, for example, if transfers are needing only to be active (ftp browser can be disconnected, while transfers continue) as there would be no point maintaing a idle connection to a ftp server unless actively using it.
The text was updated successfully, but these errors were encountered: