Task #990
openClient-side caching
Description
As a developer, I want to improve application performance and reduce server load by allowing clients to cache data.
This applies to data which do not change very often (if at all), such as "types". However, also data for which it is easy to track changes and are usually fetched together (like resources, vocabularies) could exploit client-side caching. On the other hand, caching of parameterized or rapidly changing data, like terms (which are heavily parameterized, paged) or statisics can be postponed for later stages.
Initial candidates for caching as part of this task:Term types- List of resources
- List of Vocabularies
It is expected that client-side caching based on Last-Modified and If-Modified-Since HTTP headers would be used for this task.
Updated by Martin Ledvinka almost 5 years ago
Types caching resolved by checking application store before making request for them. Not much point for server-side check for modification, as the types are loaded quickly and rarely change.
Updated by Martin Ledvinka almost 5 years ago
This task currently blocked by an issue with Apache, which strips CORS-related headers from 304 Not Modified responses, resulting in errors in the browser and the inability to correctly interpret 304 responses. See https://bz.apache.org/bugzilla/show_bug.cgi?id=51223