Newbie question... after making my first app live on the server, I noticed
updates to this app of course don't make it onto the client if the client has
accessed the app in the past. As users won't know when updates are made (which
require them to refresh their browser cache), is the best strate
just add a "cache buster" to the end of the swf url in the html. eg:
...myApp.swf?v=1
then you can just update it to v=2, v=3 etc when you have an update
On 30/10/2013 15:14, modjkl...@comcast.net wrote:
Newbie question... after making my first app live on the server, I noticed
updates to thi
Or you can fix your web server :
http://www.extravision.com/blog/whats-wrong-caching‎
Tom
On 30/10/2013 15:29, Lee Burrows wrote:
just add a "cache buster" to the end of the swf url in the html. eg:
...myApp.swf?v=1
then you can just update it to v=2, v=3 etc when you have an update
On 30/1
Thanks Lee and Tom, I had no idea... thanks for your comments.
- Original Message -
From: "Tom Chiverton"
To: users@flex.apache.org
Sent: Wednesday, October 30, 2013 8:40:28 AM
Subject: Re: is renaming app filename best way to ensure update on client?
Or you can fi
: Wednesday, October 30, 2013 8:40:28 AM
> Subject: Re: is renaming app filename best way to ensure update on client?
>
> Or you can fix your web server :
> http://www.extravision.com/blog/whats-wrong-caching
>
> Tom
>
> On 30/10/2013 15:29, Lee Burrows wrote:
> > just a
