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
Is your feature request related to a problem? Please describe.
Currently the client frequently has to check for changes on the server creating high load also for idle files.
Describe the solution you'd like
The notify_push app can solve this problem by pushing the changes to the client directly via a websocket. Therefore the latency will be highly reduced making the app even better for collaboration.
Additional context
The notify_push app is already used for file updates which are often even faster than the syncing of the text app.
The text was updated successfully, but these errors were encountered:
Yes, that would definitely be a nice integration. @icewind1991 I guess it would make sense to have a dedicated message type implemented on the notify_push side that the text app can use to push document changes to any active editing session for a document through the websocket.
Planning to tackle this as part of the y.js based collaboration rework in #2669.
There's little use in looking into it before hand as a lot of the collaboration API will change. So marking the issue as blocked by the y.js rework.
Is your feature request related to a problem? Please describe.
Currently the client frequently has to check for changes on the server creating high load also for idle files.
Describe the solution you'd like
The notify_push app can solve this problem by pushing the changes to the client directly via a websocket. Therefore the latency will be highly reduced making the app even better for collaboration.
Additional context
The notify_push app is already used for file updates which are often even faster than the syncing of the text app.
The text was updated successfully, but these errors were encountered: