[Bug 27915] Clients of WebSockets are not NTP synced (and there is no NTP-alike spec) from bugzilla@jessica.w3.org on 2015-10-01 (public-webapps@w3.org from October to December 2015)

From: <bugzilla@jessica.w3.org>
Date: Thu, 01 Oct 2015 21:26:36 +0000
To: public-webapps@w3.org
Message-ID: <bug-27915-2927-zFDvWGf9kp@http.www.w3.org/Bugs/Public/>

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27915

Domenic Denicola <d@domenic.me> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |d@domenic.me
         Resolution|---                         |WORKSFORME

--- Comment #2 from Domenic Denicola <d@domenic.me> ---
Markings as resolved per comment 1's

> Browsers rely on the system clock. Most (all?) systems I deal with these days have system clocks driven by NTP. What systems don't?

and

> You can replace Date.now by saying:

Let us know if you disagree and we can reopen.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Thursday, 1 October 2015 21:26:39 UTC