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

Improve Retry Mechanism #336

Open
jleandroperez opened this issue Aug 21, 2014 · 0 comments
Open

Improve Retry Mechanism #336

jleandroperez opened this issue Aug 21, 2014 · 0 comments

Comments

@jleandroperez
Copy link
Contributor

On error, the client should retry with a changeset including the d field, and the suspected version number.

However, if the response to that is unsucessful, it should just send with d and no version, which would cause the remote version to get completely overwritten.

This issue requires tracking of number of retries per changeset.

@jleandroperez jleandroperez added this to the v0.6.8 milestone Aug 21, 2014
@jleandroperez jleandroperez self-assigned this Aug 21, 2014
@jleandroperez jleandroperez modified the milestones: v0.6.8, v0.6.9 Aug 27, 2014
@jleandroperez jleandroperez modified the milestone: v0.6.9 Sep 9, 2014
@jleandroperez jleandroperez modified the milestone: v0.7.5 Nov 20, 2014
@jleandroperez jleandroperez modified the milestones: v0.7.5, v0.7.6 Nov 28, 2014
@jleandroperez jleandroperez modified the milestones: v0.7.6, v0.7.7 Jan 6, 2015
@jleandroperez jleandroperez modified the milestones: v0.7.7, v0.7.8, v0.7.9 Feb 4, 2015
@jleandroperez jleandroperez removed their assignment Jan 2, 2018
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