[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: Hal Murray
Subject: Re: [gpsd-dev] Updated docs on NTP segment management
Date: Fri, 27 Feb 2015 01:47:59 -0800

> This is making a good argument for all-JSON, all the time...

I can't compute with data encoded as a text string.

Is there sample code that will turn a JSON string into a struct and return a 
flag if any fields were missing?  I assume I would have to provide a table 
mapping slots in the struct to names in the JSON string.

I haven't quite put my finger on what I'm trying to suggest. (request?)

I think there are two parts to this discussion.  One is how to get the data 
from gpsd to ntpd.  The other is how to do version control.  Can we split the 
version control into two parts?  One would be between ntpd and gpsd/client.  
The other would be between gpsd client and gpsd server.

I think I'm trying to split the client side code into two parts.  The API 
between ntpd and gpsd would be between ntpd code and a small chunk of code 
provided by gpsd.  ntpd wouldn't care about the details of the version control 
between gpsd-client and gpsd-server.

These are my opinions.  I hate spam.

reply via email to

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