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.

Sign up for GitHub

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

Jump to bottom

allow clients to set UUID for a reply #3957

Closed
heartsucker opened this issue Dec 3, 2018 · 0 comments
Closed

allow clients to set UUID for a reply #3957

heartsucker opened this issue Dec 3, 2018 · 0 comments

Comments

@heartsucker
Copy link
Contributor

Description

Currently we return the UUID of a reply after the reply has been stored. In order for clients with spotty connectivity to be able to store a reply locally and then confirm it has been stored by the server, they need to have some sort of ID that is sent to the server and then returned. We might as well make this the UUID.

User Stories

As a developer working on the client, I want to be able to send a bunch of replies over a very slow / spotty connection and know which ones were stored and which ones failed.
@heartsucker heartsucker changed the title all clients to set UUID for a reply allow clients to set UUID for a reply Dec 3, 2018
@heartsucker heartsucker mentioned this issue Dec 4, 2018
Merged
1 task
@heartsucker heartsucker mentioned this issue Jan 11, 2019
Merged
@emkll emkll mentioned this issue Feb 19, 2019
Closed
17 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@heartsucker