Gary E. Miller <g...@rellim.com>: > Since you opened the door... > > > |shm | T | Shared Memory Driver > > |gpsd | T | GPSD NG client protocol > > I think that leads to confusion since they both, at least for now, > come from gpsd. And until the gpsd_json driver has sane, documented, > defaults, I fear that people will try it first with gpsd. > > Maybe: gpsd_shm, and gpsd_json. Or: shm and json. > > There could be other gpsd variants in the future.
I'm a bit resistent to this.
I don't think shm needs to change at all. It says what it is - data
coming over System V shm, which defines its own format by the shared
structure
There is in theory a better case for calling "gpsd"
something else, but in practice I think JSON is sufficiently flexible
that we'll never have a variant that's truly incompatible from ntpd's
point of view.
So I think the best value here is keeping the names short and sweet.
But my mind is open if you have a different argument.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
signature.asc
Description: Digital signature
_______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
