From 6dd58fe29a4656fabe353c5a85bb303be0f4d73e Mon Sep 17 00:00:00 2001 From: "Eric S. Raymond" Date: Fri, 16 Apr 2010 15:18:09 -0400 Subject: Delegating DBUS support to geoclue. --- www/future.html | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) (limited to 'www/future.html') diff --git a/www/future.html b/www/future.html index 24cf2995..64d87fca 100644 --- a/www/future.html +++ b/www/future.html @@ -93,6 +93,30 @@ in 2010.

serious liability if David Ludlow's Windows port actually finishes.

+

Delegating DBUS support to geoclue

+ +

We're probably going to stop shipping DBUS notifications directly +sometime fairly soon, 3.0 at the latest.

+ +

The reason for this is GeoClue. +GeoClue is an aggregator that takes geolocation-related information +from provider programs, including gpsd, and publishes +it on DBUS.

+ +

For us, DBUS support is a dusty backwater in our code. We don't +track what the DBUS community is doing or expecting. Our devteam +worries about version skew between GPSD's DBUS transmissions and +client apps, and wouldn't have the knowledge base to fix that quickly +if it happened.

+ +

The GeoClue team, on the other hand, loves DBUS and specializes +in it. We think it's probably best for both projects if they take +data from us and handle the DBUS publishing job for us.

+ +

We could be talked out of this by a solid technical argument, +but nobody has tried to make one yet.

+

Client API cleanup

This is not a near-term project.

-- cgit v1.2.1