2 ms·
If you have a lot of data to synchronize, you probably still want some kind of 'version vector' thing, which in the simple case with a centralized server, is an
by davidw 10y ago
If you have a lot of data to synchronize, you probably still want some kind of 'version vector' thing, which in the simple case with a centralized server, is an integer 'change counter' (I forget the exact term for it) that will let you fetch only the updated/new items. You'd still use a UUID for your ID though.
- mercer 10y agowouldn't filtering by date field be good enough, generally? Either way, once I realized that I use my own little todo-app constantly, a server-based implementation became necessary. I'm working on a Horizon/RethinkDB version right now which uses UUID's by default. But if that were not the case I would've probably gone for simple incrementing ID's.
- davidw 10y agoDates and distributed systems... is something you need to be careful with. Anyone have a good link summing this up? https://aphyr.com/posts/299-the-trouble-with-timestamps https://aphyr.com/posts/299-the-trouble-with-timestamps isn't bad.