From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [DBUS PATH] RemoveBonding
Date: Tue, 21 Feb 2006 18:05:11 +0100 [thread overview]
Message-ID: <1140541511.22767.11.camel@localhost> (raw)
In-Reply-To: <e1effdeb0602210649n3f391d0bgb3b6192e60ac083a@mail.gmail.com>
Hi Claudio,
> Here is the patch to remove bondings.
>
> Please check the logic. I read the BlueZ D-Bus API and the Bluetooth
> Spec, but I am not complete sure if I am covering all scenarios.
the logic looks fine to me. However it is not that important at the
moment, because we can sort out the details later.
Some small notes. The textfile_get() is not needed. Simply delete the
link key. If it fails, because it doesn't exists, this is fine. And use
hci_disconnect() instead of implementing it by yourself.
> Regarding the HCI disconnect complete event, I think we need notify
> the connected applications sending a D-Bus signal. What do you think?
We need to inform applications about the disconnect, but this is not the
job of this method. It will be done by other routines inside hcid.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-02-21 17:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 14:49 [Bluez-devel] [DBUS PATH] RemoveBonding Claudio Takahasi
2006-02-21 17:05 ` Marcel Holtmann [this message]
2006-02-21 18:09 ` [Bluez-devel] [DBUS PATCH] RemoveBonding Claudio Takahasi
2006-02-21 23:57 ` 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=1140541511.22767.11.camel@localhost \
--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;
as well as URLs for NNTP newsgroup(s).