jslifer
07-07-2003, 11:09 PM
(Searched and did not find similar request. Registered user.)
I regularly access several ftp sites which only allow a certain number of simultaneous downloads, returning a message like this:
553 Too many downloads in progress, try again later.
The problem I run into is that if I attempt to FXP from that site, the file will immediately be marked as failed and skipped. If I attempt to download directly, it immediately fails and retries the download until the download starts or it hits it's retry limit.
My suggestion is two-fold. First, when attempting FXP and encountering this, recognize the message returned by the server and don't immediately fail the files. Second, the addition of a delay setting which would be between failed file retries would alleviate the trying and retrying that pounds on the ftp server until there is an open download connection.
Thanks, JS
I regularly access several ftp sites which only allow a certain number of simultaneous downloads, returning a message like this:
553 Too many downloads in progress, try again later.
The problem I run into is that if I attempt to FXP from that site, the file will immediately be marked as failed and skipped. If I attempt to download directly, it immediately fails and retries the download until the download starts or it hits it's retry limit.
My suggestion is two-fold. First, when attempting FXP and encountering this, recognize the message returned by the server and don't immediately fail the files. Second, the addition of a delay setting which would be between failed file retries would alleviate the trying and retrying that pounds on the ftp server until there is an open download connection.
Thanks, JS