Whenever there are unconfirmed local changes, the peer should try to send them to the authority, along with its current synchronized version.
- If that version matches the server’s version, the server accepts the changes and adds them to its history.
- Otherwise, it rejects them, and the peer must wait until it receives the conflicting changes, and try again after integrating them.
Hello, everyone, the above is a quote about the principles section of the website example, my query centers on the second point (the bolded part).
Assuming that there are multiple peers editing continuously at the same time for a period of time, and that one of the peers has a poorer network than the others. Every time the authority receives an update from the weaker peers, it hits the second scenario, and then that other peers will never see that peer’s updates until all the other peers stop inputting.
I would like to know how to resolve this edge case, thanks.