-
is this how it currently works ? When opening the browser app (client) it creates a SSE connection to one of the backend instances. You have no guarantee of which one it is. The backend should send an heartbeat every X seconds to the client. If the client stops receiving the heartbeats then he can assume that the backend is down. It can then re-create the SSE connection. But you might have lost notifications... To avoid this you maybe have a timestamp or a notification id, and when re-creating the connection you pass that timestamp or id to get all the subsequent notifications from it. Nats then tries to send the sse event to the browser . I am playing around with benthos SSE plugin for Datastar . |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Correct.
No, this shouldn’t be required. |
Beta Was this translation helpful? Give feedback.
Correct.
No, this shouldn’t be required.