From: Johan Hedberg <johan.hedberg@nokia.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Implementing the PIN helper support
Date: Tue, 21 Feb 2006 15:02:40 +0200 [thread overview]
Message-ID: <20060221130240.GA11197@localhost.localdomain> (raw)
In-Reply-To: <e1effdeb0602210440p141b4b7cta5c51ca87d135bde@mail.gmail.com>
Hi Claudio,
On Tue, Feb 21, 2006, Claudio Takahasi wrote:
> Let me try expose some D-Bus features that can help us design the PIN
> Agent better...
>
> Currently PinAgent uses the system bus connection. D-Bus is able to
> start applications automatically. Applications with user interfaces
> can't be started by system dbus-daemon, only the session can run this
> kind of applications. Using the session bus connection, it is not
> necessary has a applet/or a application always active. The D-Bus
> starts the application when the first message is sent to the path.
> For more information read the section "Message Bus Starting Services":
> http://dbus.freedesktop.org/doc/dbus-specification.html
I'm aware of the activation feature of D-BUS, and if you look through
the bluez-devel archives you'll even find mails from me suggesting to
use it a year ago or so. However, it's most likely not the right
solution nor even feasible currently.
The main problem is that we can't use the session bus for
hcid/bluetoothd since the daemon is a system level service which doesn't
know about any specific session (it might become possible in the future
to discover existing session busses through the system bus, but
currently this is not possible).
Then there's the possibility of creating a bluetoothd specific interface
for the user to tell it about the existence of his session bus. However,
I have a feeling that this would over-complicate the D-BUS code, create
all sorts of extra (e.g. security related) issues, and would conflict
with the "discover session busses through system bus" feature which has
been hinted as a possible addition to post-1.0 versions of dbus (you'll
need to dig the dbus mailing list archives for the exact reference).
Johan
-------------------------------------------------------
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 13:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 20:44 [Bluez-devel] Implementing the PIN helper support Marcel Holtmann
2006-02-20 21:14 ` Johan Hedberg
2006-02-20 21:31 ` Marcel Holtmann
2006-02-21 9:31 ` Johan Hedberg
2006-02-21 11:35 ` Marcel Holtmann
2006-02-21 12:21 ` Johan Hedberg
2006-02-21 12:56 ` Marcel Holtmann
2006-02-21 12:40 ` Claudio Takahasi
2006-02-21 13:02 ` Johan Hedberg [this message]
2006-02-21 13:10 ` Marcel Holtmann
2006-02-21 13:02 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2006-02-20 20:48 Christopher E Piggott
2006-02-20 20:52 ` 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=20060221130240.GA11197@localhost.localdomain \
--to=johan.hedberg@nokia.com \
--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).