You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should have some internal data tree to cache all of the responses for INDEX requests so that if a user makes that call and then a GET/Show request that we already have, we just return that.
This would need to have some kind of expiration tracking and invalidation marking for when we make a PUT/POST request. Also will need to make available a force option and to update the internal data when we make DELETE requests.
This should be able to be turned off, and maybe disabled by default?
The text was updated successfully, but these errors were encountered:
We should have some internal data tree to cache all of the responses for INDEX requests so that if a user makes that call and then a GET/Show request that we already have, we just return that.
This would need to have some kind of expiration tracking and invalidation marking for when we make a PUT/POST request. Also will need to make available a
force
option and to update the internal data when we make DELETE requests.This should be able to be turned off, and maybe disabled by default?
The text was updated successfully, but these errors were encountered: