New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add cache on last-scans #58

Open

Hugo-C opened this issue Mar 30, 2024 · 0 comments

Owner

Hugo-C commented Mar 30, 2024

Currently the endpoint returns the full list of last scans every 5s to each users.
Etags might be a good way to improve this by:

generating an hash in redis on modifying the last scans, this effectively invalidate the ETag cache
on client query, check the Etag value to see if we return 304 or the full response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment