Xopus and Cache

Cache

Caching may occur in multiple places. Browsers have cache, but also servers can do caching. Even then there may be layers of software on the server, each performing caching operations.

Browser and servers each have their own way of caching. A browser can be configured to be very thorough when caching for example, and will thus save the file endlessly. Cache may furthermore only work for specific files. Especially when developing an Xopus implementation this may be very annoying to work with.

End User cache problems

The problem you are most likely experiencing is that the document you are editing appears not to be saved after a reload, even though you are sure you saved it. You can check if it is indeed a cache problem by clearing your browser cache.

Most of time this problem can either be resolved by changing the browser's cache settings to something a little less strong, or by adding cache headers to the server's response headers for the XML documents that Xopus loads.

Development

When developing with Xopus cache might be even more annoying since you are changing a lot of different files. Setting browser to not do any caching may be helpful.