You're talking about server-side cache? Won't help (well, not that
you'll be able to tell anyway). You might shave a few milliseconds off
the load on the server, but you'll spend many seconds on the download
part, so the few ms saved aren't relevant. I'd also look at putting that
flash file on some sort of CDN, or at least on a web server that has a
larger pipe than you likely do. Perhaps setup another domain on a web
hosting company's server, called something like bigcontent.mycompany.com
and pull the flash from there.
Of course, this is all secondary to the WTF associated with a 44MB flash
file in the first place. :-)
-Walden
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
