Bug #3748
Save to storage medium method: amend
| Status: | New | Start date: | 09/14/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  jiaz | % Done: | 0% | |
| Category: | - | |||
| Target version: | 030 - Version > 2.xxx | |||
| Resolution: |
Description
Preferred saving to storage medium should be too specify it's start (and ending) location, instead of amending data to file.
I've noticed that jD amends data to file regardless of its jD action (virgin download/resumed). I believe this is possibly one of jD hidden problems of the future, mainly because it will hinder features like pre allocation of space on disk/file. But more importantly amending data is well known for it's higher instances of data corruption. Most download managers moved away from amending data just for that reason.
Benefits of specifying save position
Supports pre allocation of required space to disk/storage medium
Supports resuming downloads from different from mirrors. (interchangeable)
Supports downloading one file from multiple file hosters (effectively chunk loading from multiple hosters)
Note
Not tested in svn, could already been addressed.
Noticed this with because of http://svn.jdownloader.org/issues/3747
Related issues