From: Bastien Nocera <hadess@hadess.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
kevin@atheros.com, David.Quan@atheros.com,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
geoclue@lists.freedesktop.org
Subject: Re: [PATCH 0/2] iw: add GeoClue support
Date: Mon, 23 Aug 2010 17:05:07 +0100 [thread overview]
Message-ID: <1282579507.3405.130.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTimrtWQKycuAcZ3SjDaOqJ6Z-pPNauRfh+2aZ=ge@mail.gmail.com>
On Mon, 2010-08-23 at 08:44 -0700, Luis R. Rodriguez wrote:
>
> > What use is a command line tool that has to talk to a whole bunch of
> > daemons etc.?
>
> The current implementation doesn't talk to deamons. The hostip
> provider within GeoClue and it will just trigger a URL get. If
> desktops start implementing a master server though then the query
> would simply be a cached response.
Note that this error carries on in the mail. There is a master provider
for Geoclue that can make use of whatever providers are available, but
it's not in too good a shape.
I'd rather somebody started fixing the Geoclue master provider rather
than relying on a particular service, especially when the D-Bus API for
the providers themselves is something we don't want to support in the
longer term.
Cheers
next prev parent reply other threads:[~2010-08-23 16:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 0:29 [PATCH 0/2] iw: add GeoClue support Luis R. Rodriguez
2010-08-21 0:29 ` [PATCH 1/2] iw: make is_alpha2() available to other objects Luis R. Rodriguez
2010-08-21 0:29 ` [PATCH 2/2] iw: add GeoClue support for automatically determining location Luis R. Rodriguez
2010-08-23 14:11 ` [PATCH 0/2] iw: add GeoClue support Johannes Berg
2010-08-23 15:44 ` Luis R. Rodriguez
2010-08-23 16:05 ` Bastien Nocera [this message]
2010-08-23 17:46 ` Luis R. Rodriguez
2010-08-23 21:05 ` Bastien Nocera
2010-08-23 22:11 ` Luis R. Rodriguez
2010-08-23 22:15 ` Bastien Nocera
2010-08-23 22:22 ` Luis R. Rodriguez
2010-08-23 22:29 ` Bastien Nocera
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1282579507.3405.130.camel@localhost.localdomain \
--to=hadess@hadess.net \
--cc=David.Quan@atheros.com \
--cc=geoclue@lists.freedesktop.org \
--cc=johannes@sipsolutions.net \
--cc=kevin@atheros.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).