I back up David's thoughts. Moreover, Isn't keeping time up to date across sever and client also difficult in a distributed system, as it may also become out of sync ? Isn't it just moving the problem ?
Regards, Benoit On Monday, June 27, 2016 at 3:22:28 PM UTC+7, D David wrote: > > Hey guys, > > So you really think we should recode the time-checking logic on all > clients? Isn't that simpler to implement only at the server-level? > > Regards, > David > > > Le lundi 27 juin 2016 03:22:51 UTC+2, Neil Jenkins a écrit : >> >> On Fri, 24 Jun 2016, at 08:44 PM, Bron Gondwana wrote: >> >> I'm generally adverse to sending calculated values like this through the >> API. >> >> >> Yes, I agree. This doesn't fit with the JMAP model, which as far as >> possible tries to avoid sending calculated values due to the difficulty in >> keeping them in sync. >> >> >> I would be happy with an API call to get the server's current time value >> >> >> I think this is a better approach if this functionality is necessary (I'm >> not entirely convinced it is, given that most devices these days sync their >> clocks via the internet, so it's rare to be skewed more than a second out). >> >> Neil. >> > -- You received this message because you are subscribed to the Google Groups "JMAP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jmap-discuss/b763ac8a-6e0a-4f0b-844c-a14333e97119%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
