[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gpsd-dev] Updated docs on NTP segment management

From: Gary E. Miller
Subject: Re: [gpsd-dev] Updated docs on NTP segment management
Date: Wed, 25 Feb 2015 18:04:03 -0800

Yo Miroslav!

On Wed, 25 Feb 2015 14:54:56 +0100
Miroslav Lichvar <address@hidden> wrote:

> > The chronyd socket is binary which brings up issues of structure
> > packing, versions, etcc.
> Yeah, I've already found some fields that I'd like to add to the
> protocol, but didn't do it to not break the compatibility.

There are the dummmy fields.

> > Would using JSON over sockets violate your 'simple as possible' 
> > requirement?
> Do we really need to use a context-free language for this? I
> personally would prefer something that can be parsed with couple
> strcmp/sscanf calls.

Gack.  gpsd tried the sscanf approach and it is very deliate.

> I think phk is planning to use a simple text protocol in the new ntpd
> replacement (ntimed) as the main protocol for all refclocks, which
> will run in separate processes. If gpsd spoke that, maybe it could be
> connected directly without having to run a special driver for
> conversion.

I suspect gpsd would support any refclock protocol we could figure out.

We (gpsd devs) would certainly like to hear any ideas.  The current
methods are problematic.

Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97701
        address@hidden  Tel:+1(541)382-8588

reply via email to

[Prev in Thread] Current Thread [Next in Thread]