From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] The new D-Bus API specification
Date: Thu, 23 Feb 2006 00:58:25 +0100 [thread overview]
Message-ID: <1140652705.4519.71.camel@localhost> (raw)
Hi,
there have been rumors about a written API specification for the D-Bus
interface of hcid (and bluetoothd in the future) and all of them is
actually true. You will find the current version under hcid/dbus-api.txt
inside the bluez-utils CVS. This isn't the final version, but it really
looks good and something about 90% has been implemented in the last few
weeks. Most of the work has been done by Claudio, Eduardo and Johan. So
thank these guys for their work.
I like to see the rest 10% implemented and after that my plan is to
release the next version of bluez-utils and open it for wider testing,
but any feedback at this point is highly welcome. And I also like to see
sample programs in various languages that we can include for reference.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2006-02-22 23:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 23:58 Marcel Holtmann [this message]
2006-02-24 19:05 ` [Bluez-devel] The new D-Bus API specification Marcel Holtmann
2006-03-02 21:02 ` Claudio Takahasi
2006-03-03 13:55 ` Marcel Holtmann
2006-03-04 20:15 ` Sjoerd Simons
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=1140652705.4519.71.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).