On Fri, 08 Jun 2001 18:13:57 -0500, Michael Kaply <[EMAIL PROTECTED]>
wrote:
>The reason this happens is so that time isn't wasted.
>
>The download starts immediately. The whole time you are deciding where to put
>the file, the download is still happening.
>
>Sometimes by the time you select where to put it, the download is already
>done.
>
>Some people like this feature some people don't
>
>Mike Kaply
>IBM
Count me in the don't like category. If it is really going to try and
be this fancy, it should start using the new location immediately
after it is specified. I assume there are implementation problems
with this. How about making a size threshold so that for "small"
files (< 1MB?) it would do temp and move, but for larger files it
would wait for a filename or buffer the first MB to RAM (hardly a dent
with mozilla's footprint). I swear NS 4 used to buffer a small amount
before or as you were entering the filename.
>Duane Chamblee wrote:
>
>> Michael Kaply wrote:
>> >
>> > Actually, what Mozilla does is download the file to your TEMP directory.
>> > Then when it is done with the download it MOVEs it to the new name.
>>
>> I had a condition where the temp file wasn't been "moved" to the save
>> location. I fixed by removing and unzipping the latest again. (I think I
>> fixed it). I thought the cause might be that my temp directory was on a
>> different volume that my "inbox" directory.
>>
>> I don't understand why this temp download happens anyway. Why not just
>> download to the saved location. (maybe because in Windows these partial
>> files can cause a desktop freeze up and downloading to the desktop?)
>
Chris Hill
[EMAIL PROTECTED]
