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
@lauft pointed out that the sync model would map well to the Git model. We could build a server implementation wrapping Git, using a similar set of files to those in the cloud storage: a latest file, a bunch of version files, and a bunch of snapshot files.
The latest file would be contentious: changing in every commit. However, that's precisely enforcing the replica invariant. Those conflicts can occur both on git pull (when new versions arrive) and on git push (if latest has changed since git pull).
The text was updated successfully, but these errors were encountered:
@lauft pointed out that the sync model would map well to the Git model. We could build a server implementation wrapping Git, using a similar set of files to those in the cloud storage: a
latest
file, a bunch of version files, and a bunch of snapshot files.The
latest
file would be contentious: changing in every commit. However, that's precisely enforcing the replica invariant. Those conflicts can occur both ongit pull
(when new versions arrive) and ongit push
(iflatest
has changed sincegit pull
).The text was updated successfully, but these errors were encountered: