Note that having perfect clocks on the server helps, but doesn't eliminate the problem.
We could assume that the token server and the storage servers have the same skew, but that's about it. The issues with network transitions, restarts, client clock changes, etc. etc. all continue to apply. We're primarily concerned with the client clock, here. On 19 Feb 2014, at 12:34 PM, Toby Elliott <telli...@mozilla.com> wrote: > This seems like the best answer beyond throwing time (and HAWK) out the > window entirely. We're carrying baggage from multiple different machines; > asking the client to sort that out seems doomed. > > It's unlikely to be an issue for external users, as their install will all be > on the same box in most cases. _______________________________________________ Sync-dev mailing list Sync-dev@mozilla.org https://mail.mozilla.org/listinfo/sync-dev
