3 ms·
The problem as I've understood it is conflict resolution, not diffing. Rsync only does one-way sync so it does not help much here.
by SahAssar 6y ago
The problem as I've understood it is conflict resolution, not diffing.
Rsync only does one-way sync so it does not help much here.
- contingencies 6y agoI guess you can have a distributed locking mechanism, either scope or line-driven. Another option would be when there is a conflict you have a fork, and then re-merge at a later point (eg. when scope-specific changes are complete or scope is left or syntax is re-evaluated as valid), more similar to git style workflow. Which begs the question, why not just use an established RCS/VCS like git and build the interface in front of it, utilizing its built-in diff? However, this workflow probably detracts greatly from the real time intent...
- SahAssar 6y ago> I guess you can have a distributed locking mechanism, either scope or line-driven In real time? How would that solve the problems outlined in the article? > However, this workflow probably detracts greatly from the real time intent Seems like you understand the problem.
- monroewalker 6y ago*raises the question https://en.wikipedia.org/wiki/Begging_the_question https://en.wikipedia.org/wiki/Begging_the_question