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 Chat message reliability #5551

Merged
merged 2 commits into from Jun 17, 2021
Merged

Improve Chat message reliability #5551

merged 2 commits into from Jun 17, 2021

Conversation

ghost
Copy link

@ghost ghost commented Jun 2, 2021

As described in #5526, there are cases where network messages get the arrived status but no ACK and the receiver never actually saw the message. This can be cause of confusion because the "arrived" status is generally used by the sender as indication that all is good. The ACK is generally ignored.

To remedy this for Chat messages, this PR displays the sent message as "In transit" until the ACK is received back, or it times out and displays status describing the problem and asking the user to try again. The timeout is 5 seconds. An ACK can still be received after 5 seconds, in which case the status will update to show that the message arrived.

Screenshots

Sent the message, waiting for the ACK:
image

ACK received back:
image

No ACK received back:
image

@ripcurlx ripcurlx added this to the v1.6.6 milestone Jun 7, 2021
@ripcurlx
Copy link
Contributor

ripcurlx commented Jun 7, 2021

utACK from code perspective. @m52go Could you please review the text changes? Thanks!

Co-authored-by: m52go <735155+m52go@users.noreply.github.com>
Copy link
Contributor

@ripcurlx ripcurlx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

@ripcurlx ripcurlx merged commit 1a59e92 into bisq-network:master Jun 17, 2021
@ghost ghost mentioned this pull request Jul 2, 2021
@ghost ghost mentioned this pull request Jul 18, 2021
@ghost ghost deleted the chat_msg_ack branch May 29, 2022 22:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants