Return-Path: Date: Thu, 17 Aug 2006 15:45:14 +0300 From: Johan Hedberg To: BlueZ development Message-ID: <20060817124514.GA27427@localhost.localdomain> References: <20060816153432.GA13691@srcf.ucam.org> <1155770177.4075.102.camel@aeonflux.holtmann.net> <20060816214606.GA21719@srcf.ucam.org> <1155819360.4075.123.camel@aeonflux.holtmann.net> <20060817113538.GB5118@srcf.ucam.org> <1155823499.4075.157.camel@aeonflux.holtmann.net> <20060817122559.GA6422@srcf.ucam.org> MIME-Version: 1.0 In-Reply-To: <20060817122559.GA6422@srcf.ucam.org> Subject: Re: [Bluez-devel] DBus interface - determining whether a device exists Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net Hi Matthew, On Thu, Aug 17, 2006, Matthew Garrett wrote: > The problem isn't just in actually setting up the connections, it's in > providing the information about available devices to other applications. > Nowadays, the right layer for device enumeration is HAL. If I tell my > system about a mobile phone, then the correct behaviour is for it to > appear as a HAL object. In order for Network Manager to offer me the > choice of connecting via my phone, the phone needs to be in HAL. So, > somehow, at login time the phone needs to be added. > > There's two ways of dealing with this. The one that I prefer is that we > make some effort to determine that the phone actually exists, and then > add it to HAL in the same way that we would if we'd just done device > discovery and the phone was discoverable. This needs us to have some > mechanism for determining whether the phone actually exists. The second > is that we store the HAL data and repopulate HAL at login time. This is > more hacky, since we're adding information without even having made a > token effort to determine whether the device exists or not. > > I guess that since we don't have any guarantees that the device exists > at any given point in time anyway, this makes less difference and we > should just populate HAL regardless. I suppose I'm open to that. Maybe you could simply use the list of bonded devices to populate HAL? You could use the ListBondings method and BondingCreated/BondingRemoved signals for that. Johan ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel