Open antoniomuso opened 1 year ago
Good, but I think this has higher priority #7, no?
Yes, it has, but #7 is the more complicated feature because it depends on #8 , And to do this, we have to create a backend part for this plugin with a Processor. The Processor should enrich the component with the GitLab project-id.
@antoniomuso all clear, thank you
This could benefit from an LRU cache instead of a fixed for all TTL!
I am just thinking of simply changing the cache policy of fetch
https://developer.mozilla.org/en-US/docs/Web/API/Request/cache#value
I am just thinking of simply changing the cache policy of
fetch
https://developer.mozilla.org/en-US/docs/Web/API/Request/cache#value
Which did you have in mind? Could possibly help out with this 👍
Now that we have the backend part, we can handle caching from the server side. This can be done by changing the cache-control
header with TTL equal to 0 with a TTL of 10 seconds. We can also allow the user to configure a custom TTL in the app-config.yaml
.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
We can add request caching with a lower TTL to reduce the number of duplicated requests.
This should also be done by caching the stale responses.