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
We should add ping/pong in Realtime. According to Websocket Client, these can serve as a way to keep a connection active even if data is not being transmitted. Why we need this? I have tested the Realtime in appwrite if you redirect on this Link. You can see the reason that this feature is needed.
In the SDKs, I think we must add another parameter called pingInterval. This will be the basis on periodic to trigger the ping
This should really get picked up else Realtime is unusably broken in terms of reliability. It expects a ton of management from the app developer to ensure it works. I have never had such issues with Firebase
This should really get picked up else Realtime is unusably broken in terms of reliability. It expects a ton of management from the app developer to ensure it works. I have never had such issues with Firebase
yeah I think realtime in appwrite not so good. Does not yet a feature of filtering and all the permissions that you settled in documents and files are useless in realtime. I think the team should focus on improving the Realtime😔
🔖 Enhancement description
We should add ping/pong in Realtime. According to Websocket Client, these can serve as a way to keep a connection active even if data is not being transmitted. Why we need this? I have tested the Realtime in appwrite if you redirect on this Link. You can see the reason that this feature is needed.
In the SDKs, I think we must add another parameter called
pingInterval
. This will be the basis on periodic to trigger the ping🎤 Pitch
The use case has been tackled here
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: