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 Documentation on what to do to guarantee message delivery #1010

Open
kyeshmz opened this issue May 21, 2024 · 4 comments
Open

Improve Documentation on what to do to guarantee message delivery #1010

kyeshmz opened this issue May 21, 2024 · 4 comments
Labels
documentation Improvements or additions to documentation

Comments

@kyeshmz
Copy link

kyeshmz commented May 21, 2024

Improve documentation

Link

Add a link to the page which needs improvement (if relevant)

Describe the problem

The README states

Does this server guarantee message delivery?
The server does not guarantee that every message will be delivered to your clients so keep that in mind as you're using Realtime.

but there are not real clear work arounds to this.

Describe the improvement

Are there any ways to improve or make sure that the message is delivered?
Are there examples of using ack arguement for broadcast and retrying the request?

Additional context

Add any other context or screenshots that help clarify your question.

@kyeshmz kyeshmz added the documentation Improvements or additions to documentation label May 21, 2024
@kyeshmz
Copy link
Author

kyeshmz commented May 21, 2024

Also, fingers crossed for all of the issue spam the team must be facing right now

@filipecabaco
Copy link
Contributor

Hi sorry for the late reply.

At the moment we are not able to guarantee the delivery. We might be able to add it in the future if we persist the messages and the acks from listeners but that is still far away from our goals as our priorities now is launching Realtime Authorization and improve Postgres Changes

@kyeshmz
Copy link
Author

kyeshmz commented Jun 23, 2024

Could you provide me with a overall pseudo code that you would implement if you were in my shoes? Like timestamp, ack, etc?

@filipecabaco
Copy link
Contributor

what would be the size of the message sent? there might be some ways to do this but it will depend on the payload

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants