From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] CreateSecureDevice
Date: Tue, 4 Mar 2008 23:25:44 +0100 [thread overview]
Message-ID: <F5766422-47CD-4AD6-8C71-AD7D21BDB4BD@holtmann.org> (raw)
In-Reply-To: <fb2ac3c90803041411k3ea1426cib1e729b19053adce@mail.gmail.com>
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
next prev parent reply other threads:[~2008-03-04 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 22:11 [Bluez-devel] CreateSecureDevice Andrew Jorgensen
2008-03-04 22:25 ` Marcel Holtmann [this message]
2008-03-04 22:40 ` Andrew Jorgensen
2008-03-06 10:56 ` Marcel Holtmann
2008-03-06 15:54 ` Andrew Jorgensen
2008-03-07 18:39 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F5766422-47CD-4AD6-8C71-AD7D21BDB4BD@holtmann.org \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox