As I inspected the atom-pair's code, I found the core implementation is recording changes in Atom's callback function and then push change-event into queue. When some other clients receive the event, they just extract the data and apply using Atom's buffer.
I did not find the conflict resolving logic inside this package, is it possible that Atom resolve conflicts by itself?
Problem solved after I tested this package. Well, it seems this pakcage does not resolve editing conflicts produced by multiple uses, i.e. users who are editing the same file may get different file contents.
Well, I developed a package which uses ShareDB to support OT, it is now available as coeditor in atom.io, hope it can help someone who needs a collaborative editing package:)
Hi, I am new to Atom and package development.
As I inspected the atom-pair's code, I found the core implementation is recording changes in Atom's callback function and then push change-event into queue. When some other clients receive the event, they just extract the data and apply using Atom's buffer. I did not find the conflict resolving logic inside this package, is it possible that Atom resolve conflicts by itself?
Thanks.