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

Cached Data Invalidation #3

Open
jakeprem opened this issue Jul 20, 2015 · 0 comments
Open

Cached Data Invalidation #3

jakeprem opened this issue Jul 20, 2015 · 0 comments

Comments

@jakeprem
Copy link
Collaborator

This seems like a relevant thing to implement in the app.

Several scenarios/ways to implement:

  1. Invalidate record based on new data.
    1a. Could be used based on the Date_modified field on the JSON response returned by the REST API.
    1b. Could use a new API endpoint, such as /crm/PARTNER_ID/modified, or something similar. This would be ideal because cached data could be validated/invalidated without doing a full request, thus saving data.
  2. Have a set timeout on the data, e.g. every 24 hours the data is invalid and needs to be repulled.

Cache invalidation of some sort will be important at some point once we start adding and modifying data in the app, as we will have to decide whether the local data or the server data is more recent and which set of data is considered authoritative.

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

No branches or pull requests

1 participant