Hal Murray <hmur...@megapathdsl.net>:
> Or maybe a json designed for ntpd rather than gpsd.
I like that plan. (As long as there's a receipt-timestamp field
so the client can compensate for parse latency.) All the issues that
make JSON a good choice for GPSD bear on this, too, IMO.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
My work is funded by the Internet Civil Engineering Institute: https://icei.org
Please visit their site and donate: the civilization you save might be your own.
_______________________________________________
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
