- From: <bugzilla@jessica.w3.org>
- Date: Thu, 29 Jan 2015 23:05:52 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27915
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ian@hixie.ch
--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> ---
Browsers rely on the system clock. Most (all?) systems I deal with these days
have system clocks driven by NTP. What systems don't?
You can presumably layer NTP-like behaviour on top of a combination of
WebSocket and WebRTC. This doesn't seem like something that need be baked into
the protocol (just like it's not baked into TCP or UDP).
You can replace Date.now by saying:
Date.now = function () { ... }
Indeed you can replace Date entirely if you like.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 29 January 2015 23:05:53 UTC