Bug #66969

Improve overwrite behavior

Added by pspzockerscene over 5 years ago.

Status:NewStart date:07/15/2015
Priority:NormalDue date:
Assignee:-% Done:


Target version:-


A friend reported this to me though his case might be a special case.
Let's say "if file exists" is set to "overwrite" and a user attempts to download something that already exists e.g.
Now JD will first delette the existing file, then download the new one.
Now what if the new download fails or is offline?
Then the old data is lost.

His suggestion was to keep the old file and only delete it of the new download was successful.
Issues IU see coming up with this are:
-We need even more HDD space - that kinda fucks up the calculation
-What if the user restarts JD in between? We have to save even more data to keep track of such cases!
-How to behave if the user resets a link and the old file is still stored?

Just asking for your opinions on this.

Related issues

Related to Feature #77001: Controlling: add new SkipDueToAlreadyExistsAction action Rejected 02/01/2016

Also available in: Atom PDF