#Add Listener for "Realtime got disconnected"?
9 messages · Page 1 of 1 (latest)
We are experiencing some disconnects due to us moving to cloudflare not to long ago. We are working on some improvements right now like heartbeat messages and control over logging.
Right now the realtime connection in the sdk will immediately reconnect, however we don’t have an issue way to listen right now ☺️
Thank you. I guess I'm more interested in the general behavior of the disconnect though. To be concrete: when disconnected, will the events that happened during this time be replayed after the Realtime is connected again? Or will I miss out on them?
They won't be replayed.
thank you. And a follow up to my initial question: in the Node SDK, I guess there's no way I can detect when the Websocket connection was closed, right? I would manually want to fetch the latest documents in that case to make sure the client is up-to-date
Do you mean web sdk cuz node.js sdk does not support realtime
yes sorry my bad. I meant the appwrite package.
Any idea by when we can expect see something rollout specifically for self hosted ? I am really struggling with flutter web and getting realtime to work reliably. I am hopeful that any improvements will really help improve the experience ..
We are fixing 2 different things. I have create 2 PR's for adding a heartbeat to the websocket connection, so it doesnt get closed by inactivity using cloudflare for example:
These are simple to add, because there is no changes to public interfaces. However adding listeners needs more thought, because it needs to be present for all client sdk's and needs some planning.