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] [PATCH] dbus.c: cleanup/fix method parameter getting In-Reply-To: <1131368088.5824.116.camel@blade> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <20051105124837.GA27883@localhost.localdomain> <1131315924.5824.14.camel@blade> <20051107093436.GB6845@localhost.localdomain> <1131359661.5824.97.camel@blade> <20051107121354.GA9950@localhost.localdomain> <1131368088.5824.116.camel@blade> 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: Mon, 7 Nov 2005 12:12:07 -0200 Hi guys, I was trying understand all discussed things in this email... Sorry if I am writing irrrelevant thing. :) More than one client is not a common scenario, but we need handle it! IMHO, control a per D-Bus client connection will be a little bit hard, why not support Inquiry, PeriodicInquiry with more than one signature? In the current implementation is easy make this change. Use a per client connection identification will be nice if we have a peer responses instead of using signals. This will be nice when the kernel cache can be retrieved. I didn't understand how the client id works. Could you explain a little bit more? Every time that a client establish a connection with the d-bus daemon the connection id changes. Therefore control client id is useful only for clients that is always connected with the daemon. Regards, Claudio. On 11/7/05, Marcel Holtmann wrote: > Hi Johan, > > > > The num_responses and the IAC should be separate setting. It would be > > > great if this setting is specific to the D-Bus session of the caller.= In > > > this case every D-Bus user can have its own settings. Do you think th= is > > > is possible? > > > > Sure. We could either maintain a table of settings for each D-BUS peer > > using the unique name that the bus assigns for each connection, or we > > could also do the settings based on the unix user id of the client > > application (using the dbus_bus_get_unix_user function). > > I prefer the per each D-Bus peer thing, because this gives us the most > flexibility for the applications. A general per user settings would be > nice too, but maybe a little bit too much at the moment. Can you try to > implement it and send me a patch. > > Regards > > Marcel > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. Downl= oad > it for free - -and be entered to win a 42" plasma tv or your very own > Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Bluez-devel mailing list > Bluez-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bluez-devel > -- --------------------------------------------------------- Claudio Takahasi Instituto Nokia de Tecnologia - INdT ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel