Transport-agnostic client-server clock synchronization.
Maybe your client application merges real-time streams from a server with locally-generated data. Or you want to determine just what the server thinks it is "now", so that you can correctly graph real-time values.
Client or server might not be NTP-synchronized, even these days. If that's the case, you may find Clocksy useful and unobtrusive.
- Simple algorithm: timestamp at the client, timestamp at the server and send back, measure round-trip time, estimate server time and apply an IIR filter to improve accuracy over time.
- Transport-agnostic: use it on top of your own transport layer: HTTP, WebSockets, MQTT, whatever.
- Simple implementation: since it leaves transport on the user's hands, it is exactly 5 LOCs for the server, ~70 for the client.
- Automatic requests, typically converging to < 10 ms in a few iterations.
- Automatic background tab detection: Chrome goes bonkers with –sorry, optimizes– timers on background tabs, interfering with clocksy's algorithm. Automatic clock updates are switched off while a tab is hidden.
$ npm install --save clocksy
Example usage with socket.io: just call ClocksyServer.processRequest()
and return the result to the client as fast as you can:
import { ClocksyServer } from 'clocksy'; // const { ClocksyServer } = require('clocksy');
const clocksy = new ClocksyServer();
// ...
socket.on('MSG', msg => {
const { type, data } = msg;
if (type === 'CLOCKSY') {
socket.emit('MSG', {
type: 'CLOCKSY',
data: clocksy.processRequest(data),
});
return;
}
// ...
})Enable/disable automatic requests by using ClocksyServer.start|stop()
and pass any response you get from the server to Clocksy, as fast as you can:
import { ClocksyClient } from 'clocksy'; // const { ClocksyClient } = require('clocksy');
const socket = socketio.connect(url);
const clocksy = new ClocksyClient({
sendRequest: req => socket.emit('MSG', { type: 'CLOCKSY', data: req }),
// Other parameters and their default values:
// alpha: 0.2, // higher levels accelerate convergence but decrease accuracy
// updatePeriod: 10000, // [ms] how often should Clocksy estimate clock error
});
socket.on('connect', () => clocksy.start());
socket.on('disconnect', () => clocksy.stop());
socket.on('MSG', msg => {
const { type, data } = msg;
if (type === 'CLOCKSY') {
const tDelta = clocksy.processResponse(data);
// tDelta is the estimated server time minus the local time.
// Use this delta for whatever purpose you want, e.g.
// correcting the local time for graphs or changing the timestamps
// of data downloaded from the server...
// If you don't need the delta immediately, you can also obtain it later
// calling clocksy.getDelta())
return;
}
});- timesync: provides more functionalities, but is apparently more complex.
Copyright (c) Guillermo Grau Panea 2016
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.