Add option to pass HTTP headers to API calls #106
Closed
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.
Suggested implementation for #79.
Tested and working.
Summary:
Each Google API response has a E-tag attached to it, which is included in the JSON response.
If you save the response along with this E-tag, you can later check if the content of the response that you previously saved has has changed or not on the server, by adding the "If-None-Match" HTTP header to the API call. If the content has not changed, the API server answers with the code "304 not modifed".
This is a simple way to keep data retrieved from the API up to date.
The code of the API call would look like this: