Return-Path: Message-Id: From: Marcel Holtmann To: BlueZ development In-Reply-To: Mime-Version: 1.0 (Apple Message framework v919.2) Date: Tue, 4 Mar 2008 23:25:44 +0100 References: Subject: Re: [Bluez-devel] CreateSecureDevice 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 Andrew, > I was wondering why there is a CreateDevice in org.bluez.input.Manager > if CreateSecureDevice will fall back to the same behavior if the > device in question does not support secure pairing. > > bluez-gnome switched to CreateSecureDevice after that method was added > which broke users who still had older bluez-utils (no changes to > require a newer bluez-utils were made). Would it not have been better > to just add the security routines to the existing CreateDevice? Is it > too late to change this now? yes, it is too later and it would have broken the API. If CreateSecureDevice returns with no such method error, you can always fallback to CreateDevice. Regards Marcel ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel