-
Notifications
You must be signed in to change notification settings - Fork 28
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.
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
Add ETag support to the Storage
implementation
#128
Comments
This might require some thinking:
|
I played around with this a bit and I think as long as we continue to use a fileserver the |
Serving files is a perfect use case for
I think even if we decide to implement server side filtering of
|
Closing this issue as obsolete as it has been discussed and consensus reached that the combination of using the pairing of For more context, see the discussion here: https://kubernetes.slack.com/archives/C0181L6JYQ2/p1694786005446749 |
As a follow up to #113, we should add ETag support to the HTTP server. This will allow clients to poll for changes using the ETag and only fetch all the catalog contents when something has changed. This would likely be middleware that we wrap our HTTP handler with.
Acceptance Criteria
Storage
implementation is updated to use middleware to enable ETag support on the HTTP server. This can be custom middleware or middleware provided by an external packageThe text was updated successfully, but these errors were encountered: