Caching

Api2File utilises disk and memory caching to speed up requests for data that has previously been retrieved from an API.

The cache within Api2File is used at multiple levels.

• Dynamic Directory Name data
• Raw API Responses
• Transformed API Responses

The cache respects the caching headers set by the API. If required the caching can be overridden on a per-share basis, either preventing caching altogether, or enforcing a minimum cache duration for data.

It is acceptable to clear the cache directory (of all .hdr, .data and .db3 files. Simply stop Api2File and delete the files from the cache directory. When Api2File is restarted, new cache files will be created as APIs are accessed.