I personally use a build system as I have far too many files to update manually. Versioning your static resources is one of the options. This is a shameless plug but you can check out the source of my website which is a django application written in Ext to see the versioning in action. Versioning should also be done with your component/application level scripts as well. Make sure to check out the "Add an Expires or a Cache-Control Header" section which talks about versioning. Here is a really good write up on deployment level web devlopment. When you upgrade your to Ext 4.2 for example it would be : It would have a cache header that never expires and when you update to another version the name will have changed and it will force the browser to load the new file. You are going to want to version you ext file when you deploy. You can then do some load failure handlers (aka, their code still tries to load 3.0), and present a message gracefully at that point. When upgrade time happens, I rename the app b3.1-myapp, and move the app directory. This however is very good when you are in development and code changes regularly.įor the rarely changing app, I use a custom application name ("aka, b3.0-myapp") and include all the app files in the b3.0-myapp directory. This can have some negative effects if you application changes rarely (every 3 months or so), but you are forcing users to download MBs of application files for every load. This will cause your browser to fetch each file anew on every load. ExtJS itself supports a "no-cache" option that can be configured via an application load configuration. This is a common problem as web browsers are "greedy" cache-ers and will go through great lengths not to use updated versions. It seems like you are running into issues with the browser caching older versions of your application and resource files.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |