3 ms·
Sure, there's plenty of complexity there too. For simplicity, I was just assuming timestamps are fine, and we're not concerned about apparent concurrent events
by agg23 3y ago
Sure, there's plenty of complexity there too. For simplicity, I was just assuming timestamps are fine, and we're not concerned about apparent concurrent events or incorrect timestamps from a host.
- iudqnolq 3y agoYour crdt library should be maintaining some kind of logical timestamp. I'd put that in your event and use it to order. That way you get a consistent view of time. (For example yjs calls this a state vector. Might also be called a Lamport timestamp or a vector clock.)