From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Cc: kde-bluetooth@liste.ferrara.linux.it
Subject: Re: [Bluez-devel] Bluetooth MIME types and URIs
Date: Fri, 08 Jul 2005 16:47:32 +0200 [thread overview]
Message-ID: <1120834052.18553.123.camel@pegasus> (raw)
In-Reply-To: <e1effdeb05070805454b8960b6@mail.gmail.com>
Hi Claudio,
> Basically two bus type are available: system and session.
> System bus is not able to start applications with user interfaces
> because the dbus-daemon is running with root permissions.
why is activation not working with the system bus. However we might have
to use system and session bus at the same time.
> Use DBUS for request BlueZ services will be nice because it's
> possible handle security issues and concurrency.
This is the basic idea and it is the reason for putting everything
inside bluetoothd and designing a new kernel interface.
> DBus signal can be used to notify all D-BUS registered applications about
> new devices, new services, connection problems, ...
The new InquiryResult and RemoteName signals are implemented in hcid for
testing. Start "dbus-monitor --system" and call "hcitool scan".
> D-Bus is under development and some changes can occur, but it's
> possible develop some workarround to make the application compliant
> with Dbus 0.34, 0.33 and 0.23.
I already did that, but I am not very happy with it. I actually really
like to see the 1.0 release of their API.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-07-08 14:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-07 14:42 [Bluez-devel] Bluetooth MIME types and URIs Marcel Holtmann
2005-07-07 17:00 ` Fred Schaettgen
2005-07-07 18:13 ` Marcel Holtmann
2005-07-08 1:15 ` Fred Schaettgen
2005-07-08 6:38 ` Marcel Holtmann
2005-07-08 12:45 ` Claudio Takahasi
2005-07-08 14:47 ` Marcel Holtmann [this message]
2005-07-08 16:23 ` Claudio Takahasi
2005-07-08 19:10 ` Marcel Holtmann
2005-07-08 20:04 ` Claudio Takahasi
2005-07-08 20:11 ` Marcel Holtmann
2005-07-08 12:51 ` Fred Schaettgen
2005-07-08 14:43 ` Marcel Holtmann
2005-07-08 15:54 ` Fred Schaettgen
2005-07-08 19:17 ` 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=1120834052.18553.123.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=kde-bluetooth@liste.ferrara.linux.it \
/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