Currently, if caching is enabled, when issuing an API request that has previously been called the LDA will respond with the cached result.
If wanting to test, debug, or measure timing, you generally do not want the cached result, you would want the LDA to compute a new result. Currently, the only way to turn caching off is to restart the LDA with caching configured to be disabled.
Likely solution would be to add a query variable to the incoming request (e.g., '_usecache', '_bypasscache'?) to allow the use of caching to be controlled per API call. The default would be use use caching.
Currently, if caching is enabled, when issuing an API request that has previously been called the LDA will respond with the cached result.
If wanting to test, debug, or measure timing, you generally do not want the cached result, you would want the LDA to compute a new result. Currently, the only way to turn caching off is to restart the LDA with caching configured to be disabled.
Likely solution would be to add a query variable to the incoming request (e.g., '_usecache', '_bypasscache'?) to allow the use of caching to be controlled per API call. The default would be use use caching.