-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add presence-related properties #27
base: master
Are you sure you want to change the base?
Conversation
Is the Related discussion in ottypes/json1#9 Also, my gut feeling is that The |
I agree that Re |
From what I've seen in trying to use the presence API in ShareDB, application code is expected to pass in an already-valid presence object to Regarding |
I completely agree with what you said about
Exactly. Additionally, if I remember well, in the current presence implementation in ShareDB the presence is published only when there are no ops pending. So, if a user submits ops fast, the presence could become significantly delayed. Thanks to transforming against own ops, the other clients can immediately update the presence locally without waiting for presence messages. |
Adds 3 new optional properties, which are necessary for synchronizing presence using ShareDB.