For one thing I would make sure that your web server is sending the right cache headers on your previous version.  But your suggestion of adding a random string (like the build version) on the end is also better as a guaranteed mechanism.  You’ll notice that a lot of popular webapps do that to ensure no caching despite the fact that they probably set their cache headers as well.  IE is untrustworthy in this regard J

 

Matt

 


From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of Jonas Windey
Sent: Wednesday, September 20, 2006 10:51 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Flex swf caching

 

Hi,

 

What is the best way to ensure that, when uploading a new version of our project to the server, the client gets a new version of the swf file the next time he refreshes his browser?

To ensure that you have the latest version, we have to say that they should clear their browser’s cache and refresh, but we’re looking for a cleaner way to solve this.

I was thinking in terms of a build version in flex, that gets appended to the swf, so main.swf?build=3129 , to ensure the client has the newest version.

 

Thanks

 

Jonas Windey

Web Developer

T. +32 3 216 86 47

 

Pixco Interactive Division

T. +32 3 216 86 40

F. +32 3 216 86 49

 

http://www.pixco.com

 

__._,_.___

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com





SPONSORED LINKS
Software development tool Software development Software development services
Home design software Software development company

Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe

__,_._,___

Reply via email to