Skip to content

Improve Retry Mechanism #336

Open
Open
@jleandroperez

Description

@jleandroperez

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.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions