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
For my understanding, the client calls GetMissing and actually sends his document to the server, which then makes a diff and then gets a diff from the client and the server document.
After that the client would receive updates. But afaik this only works because the global lock. Otherwise The client could loose update messages. So would it not make more sense to send all update messages to the client and let him sort out that problem?
Basic Plan
I have started to play around with the code base a little bit. My idea would be the following:
Questions
What I don't understand is:
Initial sync process
I am talking about the following code: https://github.com/yjs/ycs/blob/main/samples/YcsSample/Yjs/YcsManager.cs#L109. Perhaps I have some issues in understanding the general yjs protocol.
For my understanding, the client calls
GetMissing
and actually sends his document to the server, which then makes a diff and then gets a diff from the client and the server document.After that the client would receive updates. But afaik this only works because the global lock. Otherwise The client could loose update messages. So would it not make more sense to send all update messages to the client and let him sort out that problem?
Scaling
I had a look to the following code: https://github.com/ueberdosis/hocuspocus/blob/main/packages/extension-redis/src/Redis.ts
So if I understand it properly, there are 2 concepts:
Then signalr would not really make sense I think.
The text was updated successfully, but these errors were encountered: