The problem is xml caching, which can be fixed with the "cachebuster" trick. Where you have the path for the XML, use:
'http://www.sitename.com/info.xml?cachebuster='+new Date().getTime(); Because it will generate a unique date and time every single time, it will force a fresh load of the xml file rather than grabbing the cached version. google "as3 xml cachebuster" for more info, there might be other versions of this trick as well. .m On Thu, Oct 29, 2009 at 7:39 AM, David Hunter <[email protected]> wrote: > > hi, > a while ago i did a portfolio site for a photographer which loads lots of > images using an xml file. everything works fine. when you return to the site > it loads more quickly as do the images, i guess because the browser has > cached them. but sometimes after the site has been updated (ie. photos have > been added to the portfolio and put in the xml file) it doesn't recognise > that new content is there and loads the same old photos. only after clearing > cache or private data and then returning to the site does it load the new > images. obviously this is far from ideal. > i'm not sure if its because the swf gets cached or the xml gets cached or > both. > i've just seen a note on the adobe site about using "Expires" header in an > html page or PRAGMA header to prevent the contents being cached but it would > be great to not cache the swf and xml which are very small files but cache > the images so the site runs quicker. > thanks in advance for any help, > david > _________________________________________________________________ > New Windows 7: Simplify what you do everyday. Find the right PC for you. > http://www.microsoft.com/uk/windows/buy/_______________________________________________ > Flashcoders mailing list > [email protected] > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
