You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an application which uses Soketi, a pusher-compatible Web Socket server for message delivery.
In some instances my application requires that messages are not lost. What I mean is, if the application is offline for a short period, when it comes back online it should be able to catch up on lost messages (or at least detect this and refresh all its data). My understanding is that this is not supported by the Pusher protocol - there are no sequence numbers included in the heartbeat message. Short periods of connectivity loss between Echo heartbeats could be missed, and dropped messages undetected. I am doing everything I can in my application to handle this, but my understanding is that missed messages are unavoidable at the protocol level.
I am considering alternative Web Socket servers that implement history and replay (e.g. https://centrifugal.dev/) but before I go to far, I was wondering if there are any plans to support at least once message delivery delivery in Reverb.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have an application which uses Soketi, a pusher-compatible Web Socket server for message delivery.
In some instances my application requires that messages are not lost. What I mean is, if the application is offline for a short period, when it comes back online it should be able to catch up on lost messages (or at least detect this and refresh all its data). My understanding is that this is not supported by the Pusher protocol - there are no sequence numbers included in the heartbeat message. Short periods of connectivity loss between Echo heartbeats could be missed, and dropped messages undetected. I am doing everything I can in my application to handle this, but my understanding is that missed messages are unavoidable at the protocol level.
I am considering alternative Web Socket servers that implement history and replay (e.g. https://centrifugal.dev/) but before I go to far, I was wondering if there are any plans to support at least once message delivery delivery in Reverb.
Beta Was this translation helpful? Give feedback.
All reactions