Skip to content
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

[Background Fetch] Simplify fetch storage workflow. #13528

Merged
merged 1 commit into from
Oct 18, 2018

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Oct 15, 2018

In addition, MatchAll should return all records, including unprocessed
ones. To support this, the following changes were made:

  • Creating a registration also stores all the requests with an empty
    response in the cache.
  • When an individual request is processed, the failure reason (if any)
    is stored in the metadata.
  • The logic of GetSettledFetchesTask was moved to
    MarkRegistrationForDeletionTask. It checks the metadata rather than the
    cache itself to find a failure reason (if any).
  • Match/MatchAll logic was moved to a new database task
    (MatchRequestsTask). A new API call was added to the cache storage to
    allow querying request/response pairs. If a response is found to be
    empty it will be exposed as a nullptr.

Change-Id: I631a3ef3da95117aed759a675fe591da5201eeca
Reviewed-on: https://chromium-review.googlesource.com/c/1280851
Reviewed-by: Peter Beverloo <[email protected]>
Reviewed-by: Steven Holte <[email protected]>
Reviewed-by: Joshua Bell <[email protected]>
Reviewed-by: Ben Kelly <[email protected]>
Reviewed-by: Mugdha Lakhani <[email protected]>
Commit-Queue: Rayan Kanso <[email protected]>
Cr-Commit-Position: refs/heads/master@{#600768}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Already reviewed downstream.

@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-1280851 branch 10 times, most recently from 71d65e1 to 71304cd Compare October 18, 2018 15:27
In addition, MatchAll should return all records, including unprocessed
ones. To support this, the following changes were made:
- Creating a registration also stores all the requests with an empty
response in the cache.
- When an individual request is processed, the failure reason (if any)
is stored in the metadata.
- The logic of GetSettledFetchesTask was moved to
MarkRegistrationForDeletionTask. It checks the metadata rather than the
cache itself to find a failure reason (if any).
- Match/MatchAll logic was moved to a new database task
(MatchRequestsTask). A new API call was added to the cache storage to
allow querying request/response pairs. If a response is found to be
empty it will be exposed as a nullptr.

Change-Id: I631a3ef3da95117aed759a675fe591da5201eeca
Reviewed-on: https://chromium-review.googlesource.com/c/1280851
Reviewed-by: Peter Beverloo <[email protected]>
Reviewed-by: Steven Holte <[email protected]>
Reviewed-by: Joshua Bell <[email protected]>
Reviewed-by: Ben Kelly <[email protected]>
Reviewed-by: Mugdha Lakhani <[email protected]>
Commit-Queue: Rayan Kanso <[email protected]>
Cr-Commit-Position: refs/heads/master@{#600768}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants