-
Notifications
You must be signed in to change notification settings - Fork 4
Caching
For better performance (and to reduce load on data sources), the HXL Proxy caches all of its input and output files for one hour. That means that, in the most extreme case it could nearly 2 hours for a change in your source data to appear in the HXL Proxy output.
If it is important to see changes right away, you can bypass caching by checking the Never cache box on the Recipe page. Note that your recipes may run more slowly, and you may place a heavy load on your data source if a visualisation or similar tool makes frequent requests.
Note that you will always see the latest output version when you're working on the Data recipe page (the HXL Proxy caches only input in that case).
The associated URL parameter is force, so adding "&force=on" to a HXL Proxy link will also turn off caching.
The P-code service caches for 7 days, to reduce the load on the upstream API.
Learn more about the HXL standard at http://hxlstandard.org