From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754832Ab0HWWLX (ORCPT ); Mon, 23 Aug 2010 18:11:23 -0400 Received: from [12.19.149.2] ([12.19.149.2]:27331 "EHLO mail.atheros.com" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1754309Ab0HWWLU (ORCPT ); Mon, 23 Aug 2010 18:11:20 -0400 Date: Mon, 23 Aug 2010 15:11:19 -0700 From: "Luis R. Rodriguez" To: Bastien Nocera CC: Luis Rodriguez , Johannes Berg , Kevin Hayes , David Quan , "linux-wireless@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "geoclue@lists.freedesktop.org" Subject: Re: [PATCH 0/2] iw: add GeoClue support Message-ID: <20100823221119.GC2206@tux> References: <1282350556-16523-1-git-send-email-lrodriguez@atheros.com> <1282572681.3813.3.camel@jlt3.sipsolutions.net> <1282579507.3405.130.camel@localhost.localdomain> <20100823174620.GA12375@tux> <1282597556.3405.135.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <1282597556.3405.135.camel@localhost.localdomain> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 23, 2010 at 02:05:56PM -0700, Bastien Nocera wrote: > On Mon, 2010-08-23 at 10:46 -0700, Luis R. Rodriguez wrote: > > On Mon, Aug 23, 2010 at 09:05:07AM -0700, Bastien Nocera wrote: > > > 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 see, can you elaborate on that a little? > > See the bugzillas filed against Geoclue, most of them are due to bugs in > the Geoclue master provider. > > > > 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. > > > > Would the master provider not use Dbus for gypsy, for example? > > No, I'm talking about what's exported by the providers. I don't really > care if they talk to other parts of the system using D-Bus though. I'm > talking about link 2) here. > > [App] <-1-> [Geoclue master] <-2-> [Gypsy provider] <-3-> [Gypsy daemon] Sorry I do not follow yet. Is the idea that you would prefer if client applications would never talk to providers directly and instead always used the master provider? Luis