Subject: Re: [Bluez-devel] D-BUS fixes for hcid
From: Marcel Holtmann <marcel@holtmann.org>
To: Johan Hedberg <johan.hedberg@nokia.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
In-Reply-To: <20040616124541.GA8629@kone>
References: <20040616112702.GA898@kone> <1087385828.4309.3.camel@pegasus>
	 <20040616115718.GA8420@kone> <1087388298.4309.10.camel@pegasus>
	 <20040616124541.GA8629@kone>
Content-Type: text/plain
Message-Id: <1087391183.4309.13.camel@pegasus>
Mime-Version: 1.0
Sender: bluez-devel-admin@lists.sourceforge.net
Errors-To: bluez-devel-admin@lists.sourceforge.net
Date: Wed, 16 Jun 2004 15:06:23 +0200

Hi Johan,

> I must admit that I hadn't looked into how the bluez-pin program works
> in D-BUS mode. It seems it should be running all the time to be able to
> receive any D-BUS requests, correct?
> 
> The service activation feature of D-BUS which I have talked about is
> designed to solve the problem where some D-BUS service should be
> launched on-demand. I think the pin-helper falls exactly into this
> category, and would be IMHO more elegant if it wouldn't have to be
> running all the time but would be automatically launched by D-BUS daemon
> when needed.

if we change it this way, then how do the D-Bus PIN Helper get its
information about the running X server?

Regards

Marcel


-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel