-
Notifications
You must be signed in to change notification settings - Fork 43
Can't make partial changes to rows #4
Comments
I think this is simply a misunderstanding of how crdt works |
That is a bug. |
@dominictarr does that mean that if we send crdt messages over UDP then messages can arrive in the wrong order and not get applied? |
yeah, scuttlebutt depends on correct ordering. if you where using udp, I'm assuming for an action game, you might have On Mon, Aug 27, 2012 at 9:49 AM, Raynos notifications@github.com wrote:
|
@dominictarr I'm going to assume this is a non issue because I havn't reproduced it recently. |
Consider peer X and peer Y which each have a row.
Now let peer X do row.set("one", "one") and peer Y do row.set("two", "two")
This propagates messages [row.id, { one: one }, ts1, source] and [row.id, { two: two }, ts2, source]
For normative purposes let ts1 < ts2
Now if any peer gets these messages in order of ts2 followed by ts1 then we lose the set("one", "one") message because it's older and ignored.
The text was updated successfully, but these errors were encountered: