Return-Path: Message-ID: Date: Tue, 4 Mar 2008 15:11:52 -0700 From: "Andrew Jorgensen" To: bluez-devel@lists.sourceforge.net MIME-Version: 1.0 Subject: [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 Hello, 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? Best Regards, Andrew Jorgensen ------------------------------------------------------------------------- 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