Your best friend for file transfer.Fetch
Limiting duplicate connections (5 posts)
- Started 7 years ago by dekortage
- Latest reply 7 years ago from dekortage
Hi! I've been evaluating Fetch this week. I'm glad that Fetch offers a checkbox for duplicate connections. But, is there a way to limit the number of connections? E.g. "no more than 3"? Maybe hack a preferences file someplace...?
Scott McGuire Administrator
No, there is no way to limit the maximum number of connections to a server; however, let me clarify what the "Allow duplicate connections" checkbox does.
When the "Allow duplicate connections" checkbox is unchecked, Fetch tries very hard not to open duplication connections, that is, open up more than one window to the same server. When it is unchecked, if a window to the server is already open and not busy doing a download, Fetch will reuse that window instead of opening a new window to that server.
If, however, you are downloading files from a server, and you ask for a new connection to that same server, Fetch will open a new connection to the server and allow you to start a second download from that server, regardless of the setting of the "Allow download checkbox."
When you download or upload files, Fetch never opens concurrent connections to increase the speed of the transfers. If you want to open two connections to the same server, you must manually instruct Fetch to do that by making two connections and starting two downloads yourself.
If this information doesn't answer your question, please let us know exactly what your concerns are about duplicate connections, and we'll let you know what your options with Fetch are.
I'm mainly concerned about concurrent uploads. Let me explain with an example.
This morning, I had "allow duplicate connections" turned off. I started an FTP upload of a large file. Then I realized there was a second file I wanted to upload. I dragged the second file from the Finder to the open Fetch window and assumed it would just be added to the queue after the first one was done, but it wasn't. The first file finished, and that's all.
Of course, if I select multiple files and drop them all simultaneously onto a Fetch window, it queues them up as expected. But dragging a second one onto a busy Fetch session window, does nothing (literally).
After figuring this out, I decided to experiment, and I turned on "allow duplicate connections." Then I started a large FTP upload. Shortly thereafter, I dragged a second large file onto the busy Fetch session window. Fetch opened a new session window and started a second, concurrent upload. Just for kicks, I dragged a third file onto the second session window -- and Fetch opened a third session window. Unfortunately, the sysadmin of this particular FTP server only allows two FTP connections from any single IP address, so the third Fetch session failed with an error.
So, while I like the idea of multiple connections, I'm a little stymied by them. I either want Fetch to intelligently queue up secondary files I drag onto an existing busy session, or have a way of limiting how many new session windows it opens.
Hopefully I have explained this well. Let me know if it's not clear.
Scott McGuire Administrator
Yes, thank you, that was very clear.
Unfortunately, Fetch does not have an upload queue, although that is a feature we are considering for future versions, and there is no way to limit the number of duplicate connections.
I will file a bug about the lack of an error message when you try to upload to an already busy window.
Thanks for your feedback, and please let me know if you have further questions.
- Page 1