Marc Balmer wrote:
Gypsy uses D-Bus to notify clients about location changes, sitting
on the system bus, issuing signals as the GPS data changes. This
design allows clients to only be notified about the changes they
care about and ignore the rest. Gypsy has fine grained signals, so
a client only interested in position changes will not be woken up
for any other changes like, for example, satellite detail changes.
Gypsy is designed to be usable on all manner of systems, from low
powered devices (such as Nokia N810 and Openmoko Neo) to regular
high powered desktop systems. As the signals it emits are fine
grained applications are woken up only when they absolutely need
to be, keeping power requirements to a minimum.
Gypsy was designed to fix "the numerous design flaws found in GPSD".
These are compiled at http://gypsy.freedesktop.org/why-not-gpsd.html.
So how does this compare to gpsd for real applications? I am asking
since the main gpsd developer is also an OpenBSD developer, and maybe
there are ways to fix the problems in gpsd?
Oh, and I find this rude.
I didn't necessarily agree, that's why I put it in quotes. There are
lots of things
in DESCRs that are lifted from the upstream propaganda.
The Gypsy developer doesn't like the protocol gpsd uses, nor the fact
that its
clients have to listen to every line that it spits out. So gypsy using
dbus has an event model
with 5 or so different events you can listen for. I don't see how gpsd
could be changed
without fundamentally altering gpsd's protocol. Of course if you want to
try, please feel free.
Otherwise, it's an alternative. There are lots of alternatives. Choice
is good.
