From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bluez dbus
Date: Sat, 10 May 2008 14:57:10 +0200 [thread overview]
Message-ID: <1210424230.16390.4.camel@violet.holtmann.net> (raw)
In-Reply-To: <482586CE.50107@in.tum.de>
Hi Aleksander,
> would someone please explain to me why does bluez support D-Bus? What
> are the advantages by using dbus instead of simply linking and using the
> bluez C library?
a C library has no concept of privilege separation. Every client would
have to be setuid-root since there are tasks that require root
privileges. Without a suid-root client, we would need a message passing
interface within hcid for these task. And guess what D-Bus is.
Also D-Bus provides bindings for almost every language and the license
for a Bluetooth client using D-Bus is no longer bound to the GPL.
Besides that are multiple technical reasons why D-Bus is the right
choice for a Bluetooth API.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2008-05-10 12:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-10 11:28 [Bluez-devel] bluez dbus Aleksandar Kanchev
2008-05-10 12:57 ` Marcel Holtmann [this message]
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=1210424230.16390.4.camel@violet.holtmann.net \
--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