Hi, one solution might be the following: - The web server sets a very long time to live for a resource (js, png,...) in the cache of the browser (HTTP-Response-Header " Cache-Control"), let´s say 2 years. - The Build process tags each resource with a kind of buildstamp everytime the application is built, so the filenames of the resources look like 20121002125930_application.js. - So if there´s a new build of the applications there will be new filenames that won´t be found in the cache of the browser so the browser will load the resource from the web server. I don´t know any more efficient methods to take advantage of the browser cache, but it´s a tricky solution because you will have to update all references of the tagged resources and update them too.
Cheers, Rob. -----Ursprüngliche Nachricht----- Von: Deisss [mailto:[email protected]] Gesendet: Dienstag, 2. Oktober 2012 12:34 An: Robert Nimax; [email protected] Betreff: [qooxdoo-devel] Best practice help - how to update Qooxdoo app My app is online since few months now, and a new release is about to come. When i'm doing testing, i've to use Ctrl + R to force browser cache refresh, for me it's quite ok and i don't feel any problem about that. The problem is more for final user, most of them are dummies, so i've to take a lot care of that. I try this behaviour : putting new file above previous one, this makes unchanged file to erase previous one, new version to appear next to previous, and main javascript file erased, doing so most of users are feeling quite ok, they have updated app when the browser cache refresh by itself. But, sometimes the browser cache only refresh few parts : it makes the system using the new main file, but keeping old parts, and of course, the new main file got some slight changes which makes it crashes if it try to use old parts. My question is simple : how to make a good refresh qooxdoo app on client side. If possible, avoid thooses : - remove cache manually by setting html meta, - change server cache policy for forcing erase. I would like to know if there is a way to do that is a more proper way (the best would be something which can test the current version and the new on server side and auto refresh cache only once in such case) -- View this message in context: http://qooxdoo.678.n2.nabble.com/Best-practice-help-how-to-update-Qooxdoo-app-tp7581556.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
