Add generic WebDAV metadata cache - #646
Open
taglia wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This adds a short-lived generic metadata cache for WebDAV item lookups and folder listings.
The cache is used by WebDAV handlers for repeated
PROPFIND,GET,HEAD,PUT,DELETE,MOVE, andMKCOLlookup paths, and is invalidated on write operations.Why
WebDAV clients often issue repeated metadata requests for the same paths during backup and restore workflows. Without a short-lived cache, these requests repeatedly hit Drive metadata APIs even when the state has just been fetched or mutated by the same WebDAV process.
Behavior
Tests