I have noticed that there are two locations of where temporary files are being stored during download.

1) The xx.part file is located where the download will be stored when finished and is selectable by the user.
2) The other location is in the user's temporary directory

The second location and file(s) are of concern as it appears that there is not an option to decide where these files are being stored.
Thus, when downloading a large file, I sometimes run low on disk space. This causes an error in FRD and the file does not complete
The questions that arise as a result is:

1) Why do I need 2X the space being consumed for every file downloaded?
2) How can I change the location of the 2nd location listed above?

If there is not a way to change this location, then I am writing to toss out a suggestion that there is such an option.

Thanks All

Keep up the good work.

Temporary directory is used only for extracted plugins, not for downloading files.

-------------------------------------

Well lets put it this way, even thought I desire the download to be on drive D, Drive C looses as much space as the total file size before it is completely downloaded. Thus, downloading multiple large files eats up the C Drive despite where I choose to place the file to in the end.

Example:

Drive C has 1.9GB free space
Drive D has 10GB free space

If I simultaneously download any combination of files that is greater than 1.9GB the file download will crash as Drive C will not have enough free space to hold the files, or whatever they are.

It's not unlike extracting large files from a WinRar archive. If the archive is 1GB and I choose to extract it to Drive D (a file that will be 1,5GB extracted) then I will also need 1.5GB free space in my temporary directory on Drive C. The total disk cost is 1GB + 1.5GB + 1,5GB = 4GB. A measure of extreme inefficiency.

It's not really an issue of where the space is being consumed, but rather that space is being consumed!



Edited 1 time(s). Last edit at 04/26/2010 02:57AM by iONic.