You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@flex.apache.org by mo...@comcast.net on 2013/10/30 16:14:30 UTC
is renaming app filename best way to ensure update on client?
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 strategy to simply rename the application from, say, Main.html, to Main_v1p0.html, before transferring to the server? (Then when making an update, rename again to Main_v1p1.html, for example, etc.). Is that what developers typically do?
Re: is renaming app filename best way to ensure update on client?
Posted by Prem Radhakrishnan <go...@gmail.com>.
If you are using IIS you can also do this by using cache control headers. I
use this method pretty heavily because our application gets updated quite a
bit but sometimes only a few files at a time or one module. The http
content headers allows you to specify cache headers for a file , a folder
or an entire website. I am sure this can be done in our web servers as well
but I am only familiar with IIS.
The users find it really annoying when you have to tell them to clear the
cache all the time to get an update and this is the least painful and
effective way I have found so far. Here are a couple of reference articles.
http://www.iis.net/configreference/system.webserver/staticcontent/clientcache
http://blog.johlero.eu/2011/09/03/forcing-browsers-to-revalidate-static-content-in-iis-asp-net/
http://www.39dn.com
Perfection is achieved, not when there is nothing more to add, but when
there is nothing left to take away.
- Antoine de Saint-Exupery
On Wed, Oct 30, 2013 at 12:16 PM, <mo...@comcast.net> wrote:
> Thanks Lee and Tom, I had no idea... thanks for your comments.
>
> ----- Original Message -----
>
> From: "Tom Chiverton" <tc...@extravision.com>
> 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 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/10/2013 15:14, modjklist@comcast.net wrote:
> >> 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 strategy to simply rename the application from,
> >> say, Main.html, to Main_v1p0.html, before transferring to the server?
> >> (Then when making an update, rename again to Main_v1p1.html, for
> >> example, etc.). Is that what developers typically do?
> >>
> >
> >
>
>
>
Re: is renaming app filename best way to ensure update on client?
Posted by mo...@comcast.net.
Thanks Lee and Tom, I had no idea... thanks for your comments.
----- Original Message -----
From: "Tom Chiverton" <tc...@extravision.com>
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 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/10/2013 15:14, modjklist@comcast.net wrote:
>> 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 strategy to simply rename the application from,
>> say, Main.html, to Main_v1p0.html, before transferring to the server?
>> (Then when making an update, rename again to Main_v1p1.html, for
>> example, etc.). Is that what developers typically do?
>>
>
>
Re: is renaming app filename best way to ensure update on client?
Posted by Tom Chiverton <tc...@extravision.com>.
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/10/2013 15:14, modjklist@comcast.net wrote:
>> 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 strategy to simply rename the application from,
>> say, Main.html, to Main_v1p0.html, before transferring to the server?
>> (Then when making an update, rename again to Main_v1p1.html, for
>> example, etc.). Is that what developers typically do?
>>
>
>
Re: is renaming app filename best way to ensure update on client?
Posted by Lee Burrows <su...@leeburrows.com>.
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, modjklist@comcast.net wrote:
> 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 strategy to simply rename the application from, say, Main.html, to Main_v1p0.html, before transferring to the server? (Then when making an update, rename again to Main_v1p1.html, for example, etc.). Is that what developers typically do?
>
--
Lee Burrows
ActionScripter