Skip to content
This repository has been archived by the owner on Jun 18, 2024. It is now read-only.

ETag support #48

Open
joshgav opened this issue Nov 11, 2014 · 0 comments
Open

ETag support #48

joshgav opened this issue Nov 11, 2014 · 0 comments

Comments

@joshgav
Copy link
Contributor

joshgav commented Nov 11, 2014

Integrate support for ETags.

First, need to determine what patterns are supported by each API and make sure they are uniform.

Then, logic options are:

  1. A custom method for app developer to capture and add ETags to a request. This would mean maintaining state between requests is up to developer.
  2. Cache latest ETags for retrieved entities for ourselves and by default use them again on following requests. This absolves app developer from having to maintain state in most cases. But we have to throw an error if we find an ETag mismatch and then developer has to handle.
@joshgav joshgav self-assigned this Nov 11, 2014
@joshgav joshgav added this to the v0.11.0 milestone Nov 11, 2014
@joshgav joshgav removed this from the v0.11.0 milestone May 19, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant