From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] DBUS service support - Initial library
Date: Sat, 30 Apr 2005 02:04:30 +0200 [thread overview]
Message-ID: <1114819470.8836.124.camel@pegasus> (raw)
In-Reply-To: <e1effdeb0504291520167b9bb8@mail.gmail.com>
Hi Claudio,
> My application will provide a DBUS service and
> APIs to alows user mode applications interact
> with diferent types of Wireless/Wired connections.
> This is the reason to create a BlueZ library based
> on pand and hcitool functions. My application should
> the able to retrieve bluetooth device information,
> including establish connection, disconnect, link
> status, new devices/services, ...
> The DBUS service will not be provided at BlueZ level.
>
> The current DBUS message in the hcid is used to handle
> security/authentication issues. This message has a
> different proposal. Therefore, use the same macro
> "--enable-dbus" to enable/disable is not a good ideia.
>
> Another important information is: the user mode
> application doesn't need root privileges to create
> a bluetooth connection, because it will request using
> APIs and DBUS service.
>
> Can I create a library in the pand directory and
> reuse the common codes?
> I suggest a directive like "--enable-panz" because
> this library aims provide functions to hide connection
> details.
I think you get the whole idea of D-Bus wrong and this is not about the
current D-Bus support of hcid for the PIN helper.
As I said if you wanna control something from your application via D-Bus
then make sure there is a D-Bus enabled pand service is running. If you
wanna do it at another level, then I don't see any benefit from it. Why
should we create another library only to help your special D-Bus daemon
if it is not Bluetooth only. In that case you should simply duplicate
the code and integrate it into your daemon directly. There is no need to
make things more complicate.
For me the only thing that makes sense if you enhance the pand with
D-Bus support and then you use that D-Bus interface in your application.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-04-30 0:04 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 20:00 [Bluez-devel] DBUS service support - Initial library Claudio Takahasi
2005-04-29 9:47 ` Marcel Holtmann
2005-04-29 12:26 ` Claudio Takahasi
2005-04-29 12:43 ` Marcel Holtmann
2005-04-29 22:20 ` Claudio Takahasi
2005-04-30 0:04 ` Marcel Holtmann [this message]
2005-05-01 21:16 ` Claudio Takahasi
2005-05-01 23:18 ` Marcel Holtmann
2005-05-02 15:32 ` Claudio Takahasi
2005-05-02 16:24 ` Marcel Holtmann
2005-05-09 21:31 ` Claudio Takahasi
2005-05-11 18:27 ` Marcel Holtmann
2005-05-12 9:00 ` Peter Wippich
2005-05-12 12:41 ` Marcel Holtmann
2005-05-12 16:21 ` Peter Wippich
2005-05-20 21:04 ` Claudio Takahasi
2005-05-23 10:27 ` Marcel Holtmann
2005-05-23 15:02 ` Claudio Takahasi
2005-05-24 9:07 ` Marcel Holtmann
2005-05-25 22:20 ` Claudio Takahasi
2005-05-26 9:08 ` Marcel Holtmann
2005-05-26 21:22 ` Claudio Takahasi
2005-05-26 21:40 ` Marcel Holtmann
2005-05-30 22:42 ` Claudio Takahasi
2005-05-30 23:05 ` Marcel Holtmann
2005-06-03 20:34 ` [Bluez-devel] DBUS service support - poll patch Claudio Takahasi
2005-06-03 20:38 ` Marcel Holtmann
2005-06-03 21:31 ` Claudio Takahasi
2005-06-03 22:10 ` Marcel Holtmann
2005-06-06 13:18 ` Claudio Takahasi
2005-06-14 11:37 ` Claudio Takahasi
2005-06-17 21:59 ` Claudio Takahasi
2005-06-18 23:28 ` Marcel Holtmann
2005-05-12 12:45 ` [Bluez-devel] DBUS service support - Initial library Claudio Takahasi
2005-05-12 16:23 ` Peter Wippich
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=1114819470.8836.124.camel@pegasus \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.