Hello,
I like the existing File Exists Rules feature. However, usually this is how I would decide whether to overwrite a file:
- When initially starting a new transfer (possibly of multiple files), I may choose to Overwrite All, because I want to replace all the destination files with the ones I'm uploading.
- If an error occurs during a given transfer (eg. disconnect), Flash FXP will attempt to reconnect. When connection is re-established, I want Flash FXP to Resume that file, not restart it from the beginning.
In other words, I would like to keep the current File Exists Rules when a transfer first starts, but then I would also like to have a separate set of File Exists Rules for when a transfer is trying to recover from an error.
The common scenario is you upload multiple large files on a flaky link, on a regular basis. The files already exist in the destination (and deleting them beforehand every time is inconvenient) so you want to overwrite them all; however, any individual error-retry will cause the Resume behavior for that particular file. When the queue moves on to the next item, it will overwrite it. If an error occurs on that file also, then Flash FXP should resume subsequent attempts on that file. And so on and so forth.
I'm not sure how feasible this is. I could imagine some kind of flag could be kept in the queue file to indicate whether the transfer has already started on that given file; if not, use the base File Exists Rules, and if it does, then use the secondary File Exist Rules.
