Hi Will

On 13.02.2008, at 07:47, Will Scheidegger wrote:

Hi Tom

How about creating a crawler script that "downloads" all files in the dms locally on the server (to save bandwidth and gain speed)? Like so you could be pretty sure that the files in the cache are not corrupt.

Thought about this too - but
a) on a large site with high traffic and +200 downloads it is very likely that a download is triggered and canceled before the script reaches all files
b) see below


On the other hand if you update the site twice a day this script would have to run pretty often... :-(




Concerning the bug: I'm wondering if this applies to data in the website repository too? Webpages, images, documents stored in the website repository are not delivered by the same servlet IIRC. But it would be interesting to see if these files suffer from the same shortcomings.


Yes unfortunately it does - cache implementation is the same. So beware of big downloads in combination with inpatient users (or testers...)

Cheers, Thomas


Regards,
Will

On 12.02.2008, at 20:35, Thomas Martin wrote:

Hi David

Thanks very much for your insights.

After poking around a lot I seem to have tracked down the issue that is giving the headaches:

Whenever a client is stopping the initial download of a file, the created cache results in a corrupt file. ie: if I download a (so far uncached) large pdf of 4mb and click on cancel in the download manager at 2mb the cached file has only a size of 2mb and naturally all subsequential downloads will receive a incomplete/corrupted file.

this on its own is already annoying - now toss in IE7 and downloads with a meta refresh to make 90% of your downloads corrupt. tasty!

So the only way to guarantee that this won't happen anymore is to totally disable cache on the dms (or wherever your downloads are stored) - which also rather s*cks.


Has someone an idea how to avoid this issue and still be able to work with caching?

Does this qualify as a bug and should I file a jira-entry?


brgds, Thomas




----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------

Reply via email to