-
Notifications
You must be signed in to change notification settings - Fork 66
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
Use vector clock instead of monotonic timestamp #14
Comments
Actually, it could be very useful to make the ts injectable, so it would be monotonic, or vectors. mono-ts gives you an ordering (good if you just want new values to clobber old/other), but vector clocks allows you to reason which updates are concurrent (made without knowledge of the other). Using vector clocks means you can know whether a particular pair of updates was concurrent or not, meaning you could handle them specially - this would mean some sort of merge function. |
yes @mixu please publish that! https://npm.im/vector-clock is available! |
@Raynos @dominictarr just had my morning coffee, will have the module out on npm in ~ an hour. |
@mixu badassery! |
and it's out https://npmjs.org/package/vectorclock |
https://github.com/nko3/foojs/blob/master/vectorclock/vector_clock.js#L80
@mixu can you open source just the vectorclock as it's own module?
The text was updated successfully, but these errors were encountered: