Aristotle Pagaltzis wrote: > > * Steven Lees <[EMAIL PROTECTED]> [2007-12-06 22:45]: > > Timestamps are problematic for sync because they assume that > > you can synchronize clocks across different machines. > > I suppose that’s important when you actually try to do something > where clocks across different machines need to synchronise. > > I assume that FeedSync (which I haven’t looked at) tries to cover > some such cases.
Our design approach for FeedSync is that you're not going to have different clocks in sync, but we want data sync to work anyway. That's why we use version numbers instead of timestamps. > But for tombstones, only the server’s clock matters. Agreed. That starts to be not quite as true when your server hardware is upgraded, or your successive edit requests are handled by different machines, and so on, but in practice it will mostly work (for one-way sync). Steven
