From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
In-Reply-To: <066701c8de28$51a90a70$6701a8c0@freqonedev>
References: <066701c8de28$51a90a70$6701a8c0@freqonedev>
Date: Sat, 05 Jul 2008 19:03:38 +0200
Message-Id: <1215277418.4349.1.camel@californication>
Mime-Version: 1.0
Subject: Re: [Bluez-devel] One more suggestion regarding Agent
Reply-To: BlueZ development <bluez-devel@lists.sourceforge.net>
Content-Type: text/plain; charset="us-ascii"
Sender: bluez-devel-bounces@lists.sourceforge.net
Errors-To: bluez-devel-bounces@lists.sourceforge.net

Hi David,

> There may be a valid use-case to allow for the Agent to be a separate 
> process.  However, there needs to be a way to designate the BusName of 
> the connection from the other Agent process to the System bus.

I really have no idea what you are talking about. The agent can always
be a separate process. The agent for CreatePairedDevice must be the same
process as the caller. That is on purpose.

Regards

Marcel


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel