From: "Andrew Jorgensen" <andrew.jorgensen@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] CreateSecureDevice
Date: Tue, 4 Mar 2008 15:40:54 -0700 [thread overview]
Message-ID: <fb2ac3c90803041440l75dead88y8cd8dc9d23cf66a8@mail.gmail.com> (raw)
In-Reply-To: <F5766422-47CD-4AD6-8C71-AD7D21BDB4BD@holtmann.org>
On Tue, Mar 4, 2008 at 3:25 PM, Marcel Holtmann
> 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.
Hi Marcel,
Aren't you maintaining bluez-gnome? Could you add this fallback to
properties/input.c?
I'm curious what you mean by "would have broken the API." Do you mean
if we were to remove the method now after it has been released? If so
then I agree, it's too late.
But I'm curious why a new method was added rather than new
functionality to the existing method. Are there new callbacks that
would have broken existing clients? I guess it's a moot point now
though.
Thanks,
Andrew
-------------------------------------------------------------------------
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:40 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
2008-03-04 22:40 ` Andrew Jorgensen [this message]
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=fb2ac3c90803041440l75dead88y8cd8dc9d23cf66a8@mail.gmail.com \
--to=andrew.jorgensen@gmail.com \
--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