Improve Documentation on what to do to guarantee message delivery
kyeshmz opened this issue · 4 comments
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.
Also, fingers crossed for all of the issue spam the team must be facing right now
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
Could you provide me with a overall pseudo code that you would implement if you were in my shoes? Like timestamp, ack, etc?
what would be the size of the message sent? there might be some ways to do this but it will depend on the payload