• Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

What's the time?

My proposal just…

Whenever I encounter a phrase like "just do x", I know that x will turn out to be either ludicrously complex or provably impossible :)
 
The whole point is that the system time can't be involved in any way, as it cannot be trusted. If a user has their clock set to a timezone offset several hours different from where they are, their locale set to a location several hours different in the other direction, and is accessing the Internet through a proxy server on the other side of the world from their location, you can't show them an accurate time. And as the complaint was not that the clock was inaccurate, but rather that it could be inaccurate due to relying on the system time, you're back at square one.

You can display the timezone next to the clock. Probably easier than trying to guess timezone.

The problem of accurate time still exists, you'd need to do something similar to ntp which uses system time to compute rtt to the server. Then you could compute the offset from the server time and use the system clock to provide ticks.
 
As we are now on page 4 with no agreed consensus of opinion, maybe they were right to just remove it?!
 
You can display the timezone next to the clock. Probably easier than trying to guess timezone.

The problem of accurate time still exists, you'd need to do something similar to ntp which uses system time to compute rtt to the server. Then you could compute the offset from the server time and use the system clock to provide ticks.

Which was what I suggested in my original comment. either way ho hum :bang: :throw: and :suicide:
 

Advertisers

Back
Top