From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [Bluez-devel] Implementing the PIN helper support From: Marcel Holtmann To: bluez-devel@lists.sourceforge.net In-Reply-To: <20060221130240.GA11197@localhost.localdomain> References: <1140468298.7047.52.camel@localhost> <20060220211402.GA6466@localhost.localdomain> <1140471085.7047.63.camel@localhost> <20060221093118.GA10267@localhost.localdomain> <1140521700.10008.8.camel@localhost> <20060221130240.GA11197@localhost.localdomain> Content-Type: text/plain Message-Id: <1140527420.10008.29.camel@localhost> Mime-Version: 1.0 Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net Reply-To: bluez-devel@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ development List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 21 Feb 2006 14:10:20 +0100 Hi Johan, > > 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). and who wants to decide to either start the KDE Bluetooth applet or the Gnome Bluetooth applet. This isn't a decision that should be made by a system service. As I said, let's keep the hcid/bluetoothd dumb. Regards Marcel ------------------------------------------------------- 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