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

setMetadata must refresh the object's metadata #39

Closed
robert-bor opened this Issue May 28, 2013 · 0 comments

Comments

Projects
None yet
1 participant
@robert-bor
Member

robert-bor commented May 28, 2013

This can be either done by immediately saving the metadata to the object as well (less reliable, but cheaper), or by invalidating the data so a new fetch is done (more relliable, but costs a call).

@ghost ghost assigned robert-bor May 28, 2013

@robert-bor robert-bor closed this May 28, 2013

robert-bor added a commit that referenced this issue May 28, 2013

Issue #39 / #40 - in mock mode, non-passed metadata fields will no lo…
…nger be deleted (which was the case in pre-Folsom, therefore a correct simulation). Also, whenever metadata is set, the object will be invalidated to guarantee a full fetch.

katta pushed a commit to twxkit/joss that referenced this issue Oct 6, 2014

Issue #39 / #40 - in mock mode, non-passed metadata fields will no lo…
…nger be deleted (which was the case in pre-Folsom, therefore a correct simulation). Also, whenever metadata is set, the object will be invalidated to guarantee a full fetch.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment