Closed nichtich closed 2 years ago
I think we disabled client-side caching for jskos-server because data could change very quickly and we don't know when the data will change (i.e. client requests the recently created mappings).
This would only apply here if the schemas are frequently updated and changes need to be visible in the API quickly.
Caching can be enabled or disabled (see
server.js
) but [when] does it make sense to disable caching at all?