[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gpsd-users] gpsd as gpsd client, error "Unrecognized request"
From: |
Gary E. Miller |
Subject: |
Re: [gpsd-users] gpsd as gpsd client, error "Unrecognized request" |
Date: |
Fri, 30 Jun 2017 16:50:18 -0700 |
Yo Eric!
On Wed, 28 Jun 2017 15:18:20 -0400
Larry Boyd <address@hidden> wrote:
> If someone can say for certain that a request will *always* have a
> '\r' in the last or second-to-last byte, then ideally, we could read
> until we find that byte, and then continue.
I'm a big fan of mandatory sentance terminators.
Hanging around, just in case more data is to come, seems sub-optimal to
me.
Eric: can we just make it so all gpsd json in MUSST end with a \n?
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
address@hidden Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can’t measure it, you can’t improve it." - Lord Kelvin
pgpgjj_6bIlQ6.pgp
Description: OpenPGP digital signature
- [gpsd-users] gpsd as gpsd client, error "Unrecognized request", Larry Boyd, 2017/06/28
- Re: [gpsd-users] gpsd as gpsd client, error "Unrecognized request", Larry Boyd, 2017/06/28
- Re: [gpsd-users] gpsd as gpsd client, error "Unrecognized request", Larry Boyd, 2017/06/28
- Re: [gpsd-users] gpsd as gpsd client, error "Unrecognized request", Larry Boyd, 2017/06/28
- Re: [gpsd-users] gpsd as gpsd client, error "Unrecognized request", Larry Boyd, 2017/06/28
- Re: [gpsd-users] gpsd as gpsd client, error "Unrecognized request", Larry Boyd, 2017/06/28
- Re: [gpsd-users] gpsd as gpsd client, error "Unrecognized request",
Gary E. Miller <=