Return-Path: Date: Mon, 31 Jul 2006 16:26:52 +0300 From: Johan Hedberg To: BlueZ development Message-ID: <20060731132652.GA29003@localhost.localdomain> References: <200607311518.57014.dgollub@suse.de> MIME-Version: 1.0 In-Reply-To: <200607311518.57014.dgollub@suse.de> Subject: Re: [Bluez-devel] Addition for hcid passkey dbus request 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 Daniel, On Mon, Jul 31, 2006, Daniel Gollub wrote: > i am started working for the bluez dbus integration for kdebluetooth. The > kdebluetooth pin dialog for pairing has a pin generation feature for outgoing > pairing requests. This requires that hcid also provides connection > information about the pairing. A hcid patch is attached, which sends a > enhanced passkey request with the connection direction. This requires changes > on all application which handle as passkey agents. Is there a better solution > expect dropping the pin generation feature? I think a better solution could be to add a new method to hcid for querying the connection direction (it would take the local adapter path and remote address as parameters). This way the current passkey agent interface would not have to be changed. Johan ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel