From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: From: Claudio Takahasi To: bluez-devel@lists.sourceforge.net Subject: Re: [Bluez-devel] DBUS service support - Initial library In-Reply-To: <1114819470.8836.124.camel@pegasus> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <1114768038.8836.42.camel@pegasus> <1114778617.8836.88.camel@pegasus> <1114819470.8836.124.camel@pegasus> 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: Sun, 1 May 2005 18:16:11 -0300 Hi Marcel, I suggested provide a DBUS message service in another level because I will try contribute with NetworkManager project: http://people.redhat.com/dcbw/NetworkManager/index.html I will analyze these two approachs and define the most interesting solution for my project. Thanks for your time, Claudio. On 4/29/05, Marcel Holtmann wrote: > Hi Claudio, >=20 > > My application will provide a DBUS service and > > APIs to alows user mode applications interact > > with diferent types of Wireless/Wired connections. > > This is the reason to create a BlueZ library based > > on pand and hcitool functions. My application should > > the able to retrieve bluetooth device information, > > including establish connection, disconnect, link > > status, new devices/services, ... > > The DBUS service will not be provided at BlueZ level. > > > > The current DBUS message in the hcid is used to handle > > security/authentication issues. This message has a > > different proposal. Therefore, use the same macro > > "--enable-dbus" to enable/disable is not a good ideia. > > > > Another important information is: the user mode > > application doesn't need root privileges to create > > a bluetooth connection, because it will request using > > APIs and DBUS service. > > > > Can I create a library in the pand directory and > > reuse the common codes? > > I suggest a directive like "--enable-panz" because > > this library aims provide functions to hide connection > > details. >=20 > I think you get the whole idea of D-Bus wrong and this is not about the > current D-Bus support of hcid for the PIN helper. >=20 > As I said if you wanna control something from your application via D-Bus > then make sure there is a D-Bus enabled pand service is running. If you > wanna do it at another level, then I don't see any benefit from it. Why > should we create another library only to help your special D-Bus daemon > if it is not Bluetooth only. In that case you should simply duplicate > the code and integrate it into your daemon directly. There is no need to > make things more complicate. >=20 > For me the only thing that makes sense if you enhance the pand with > D-Bus support and then you use that D-Bus interface in your application. >=20 > Regards >=20 > Marcel >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. > Get your fingers limbered up and give it your best shot. 4 great events, = 4 > opportunities to win big! Highest score wins.NEC IT Guy Games. Play to > win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=3D20 > _______________________________________________ > Bluez-devel mailing list > Bluez-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bluez-devel > ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel