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.
We're syncing yjs documents over the network. Sometimes a message is dropped and the corresponding update does not reach a party. All following updates cannot be applied and the changes from one party are not synced.
We could perform periodic resyncs - but if the interval is too big the parties would still be out of sync for a while. If it's too short the overhead of resyncs becomes too big.
Describe the solution you'd like
If yjs emitted an event whenever an update cannot be applied because a previous update is missing we could use that to trigger the resync when it is needed.
Describe alternatives you've considered
Being able to check if all updates have been fully applied on the ydoc would be another option.
Having both combined would allow for the following:
listen for the event to see if an update cannot be applied
wait for a few seconds in case messages just arrived out of order
check if all updates have been fully applied
resync if not
Additional context
We're syncing yjs docs via a legacy protocol that uses http requests. There's a lot we can do to make this more reliable and better suited for yjs. But for the time being a way to detect out of sync situations would be really helpful.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We're syncing yjs documents over the network. Sometimes a message is dropped and the corresponding update does not reach a party. All following updates cannot be applied and the changes from one party are not synced.
We could perform periodic resyncs - but if the interval is too big the parties would still be out of sync for a while. If it's too short the overhead of resyncs becomes too big.
Describe the solution you'd like
If yjs emitted an event whenever an update cannot be applied because a previous update is missing we could use that to trigger the resync when it is needed.
Describe alternatives you've considered
Being able to check if all updates have been fully applied on the ydoc would be another option.
Having both combined would allow for the following:
Additional context
We're syncing yjs docs via a legacy protocol that uses http requests. There's a lot we can do to make this more reliable and better suited for yjs. But for the time being a way to detect out of sync situations would be really helpful.
The text was updated successfully, but these errors were encountered: