Cache information responses from REST sources #5726
Merged
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.
Change
Store and use the
/information
response from REST sources per theircache-control
header.At the base of this change is a new type of setting stream:
Encrypted
. These settings are encrypted to the user and machine that the data is stored on.Based on the log file from running with and without a cached value, the time between close log lines dropped from 189 ms to 8 ms for the msstore source. This time saving should be in effect for the large majority of uses of WinGet.
Validation
Added tests across various levels of the change.
Manually verified functionality of CLI.
Microsoft Reviewers: Open in CodeFlow