Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restore ""Open new connection" for transfers #9867

Closed
cyberduck opened this issue Mar 2, 2017 · 3 comments
Closed

Restore ""Open new connection" for transfers #9867

cyberduck opened this issue Mar 2, 2017 · 3 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Mar 2, 2017

12d27f1 created the issue

Before, Transfers preferences proposed only two options:

  1. "Open new connection"
  2. "Use browser connection"

Then "Open multiple connections" appeared as a third choice, and "Open new connection" has now been removed (in last version Version 5.3.9 (23624) for instance).

Nevertheless, it would be interesting to keep the 3 possible choices, and therefore restore option "Open new connection".
Indeed, some light file transfer servers (in a set-top box for instance) are sometimes limited to 2 connections.
In such a case, "Open a new connection" is a perfect compromise:

  • Cyberduck can perform the whole download/upload file list in sequence inside the Transfers window
    whereas "Open multiple connections" would fail.
  • Meantime, the user can still browse the contents with the opened browser connection
    whereas "Use browser connection" would prevent from doing that.

Hoping this enhancement will be possible in future releases.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 3, 2017

@dkocher commented

In b1b82b1.

Loading

@cyberduck cyberduck closed this Mar 3, 2017
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 8, 2017

@dkocher commented

Milestone renamed

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 13, 2017

@dkocher commented

#9875 closed as duplicate.

Loading

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants