DescriptionGiven that some API calls can output a large amount of data, to reduce the processing overhead, it may be wise to implement per-submodule caching.
In theory it should work the same way as the chart Caching system - generate an ETag from the request and invalidate/flush whenever relevant records are updated.
Activity
2019-09-09 16:22:10
Realistically, this project's not going to see any further development (other than possibly some bug fixes for anything new that's found).
Closing any outstanding issues as Won't Fix
2019-09-09 16:22:10
2019-09-09 16:22:10