1  |   Order by index

May 5, 2001, 10:15pm

This really bugs me, I upload a file (say a midi) then use it in AW only to
find that it cannot load (because the file isn't fully uploaded) and AW just
ignores that URL so I cannot open that midi unless I wipe out my cache
(which is annoying) so, in 3.2 can the cache be smart and if some error
comes up (like a 404) then the file does NOT get cached that way and will
reload until it is fully downloaded and THEN cached.


--
My two cents,
Captain MAD Mike

May 5, 2001, 10:31pm

Some HTTP servers seem to have an incorrect or no file size
in the HTTP reply header so it might not be possible to detect
the "fully downloaded" state.

If a request results in a 404, it already will be reloaded
when you teleport to a place that doesn't exist or a red world.
If this does not work it would mean that there was no such error.

[View Quote] --
"_
|
/\
\ /
__/ /_

1  |   Order by index