EditLive cached by the Java Runtime Environment (JRE) on the user’s machine so that in the future it starts up quickly. The JRE application cache provides a long-term cache for the editor and its resources - not the browser.
So where is EditLive cached?
It depends. Where the JRE cache is located varies depending on what OS you have, what Java version you have and how it’s all configured. The Java Control Panel provides an easy way for you to view what’s in the cache and delete entries from it.
- On Windows, there should be a “Java” icon in the Control Panel directory.
- On Mac, the application is called “Java Preferences” and it’s located in /Applications/Utilities/Java/.
For more information see Sun’s documentation.
What about the resources EditLive downloads?
EditLive downloads configuration files, style sheets and images durring the corse of loading and stores them locally on disk. This cache obeys the HTTP cache control headers specified by your server and by default caches only for the lifetime of that applet instance. Refreshing the page will cause EditLive to check for updates to all of it's resources.
There is one big catch to caching these resources - if you do make changes to resources that have long cache times, those changes may not be noticed by EditLive! or visitors to your site until that cache time expires. Usually that doesn't cause problems but it is worth keeping in mind.
Fortunately, there is a simple way to force EditLive and browsers to download a fresh copy of a resource, even before it's cache time expires - simply change it's URL.
Controlling Resource Cache Lengths
How you adjust caching times depends on the server you're using. To get started, first look at this introductory article on HTTP caching which goes into some detail about how it works and the trade offs involved. There's some links to the relevant configuration options for commonly used servers at the end of the article, but you can also find information in the documentation for your server.