linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@nokia.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [PATCH] dbus.c: cleanup/fix method parameter getting
Date: Mon, 7 Nov 2005 16:54:30 +0200	[thread overview]
Message-ID: <20051107145430.GA12669@localhost.localdomain> (raw)
In-Reply-To: <e1effdeb0511070612u7555e383kaaade3f1f0c7bbd1@mail.gmail.com>

On Mon, Nov 07, 2005, Claudio Takahasi wrote:
> 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?

The id I was talking about is in practice what you get when you call
dbus_message_get_sender for a received message. The D-BUS spec. calls it
"Unique name of the sending connection".

> 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.

True, and that was also one thing I was worried about when it comes to
the practicality of that solution (the settings wouldn't be persistent
enough). So, I think using the user id might be better in this respect.

However, let me now introduce a third option which we just discussed on
IRC with Claudio: optional D-BUS method parameters. It would be quite
easy to implement the methods so that the client could leave out most
parameters in which case hcid (or bluetoothd) would use some set of
default values. You could e.g. call the Inquiry method without any
parameters and it would just work (kind of the same way that dbus-test
allows doing "./dbus-test Inquiry" in which case it uses length=10 &
num_resp=100 as the default values). If the client insists on using its
own values for the method it would simply include them in the method
call.

In case this variable parameters solution doesn't work out for all
scenarios it could probably happily co-exist with the per-user id
settings solution.

Johan


-------------------------------------------------------
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

  reply	other threads:[~2005-11-07 14:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-05 12:49 [Bluez-devel] [PATCH] dbus.c: cleanup/fix method parameter getting Johan Hedberg
2005-11-06 21:40 ` Marcel Holtmann
2005-11-07  8:37   ` Johan Hedberg
2005-11-07  8:56     ` Marcel Holtmann
2005-11-06 22:25 ` Marcel Holtmann
2005-11-07  9:34   ` Johan Hedberg
2005-11-07 10:34     ` Marcel Holtmann
2005-11-07 12:13       ` Johan Hedberg
2005-11-07 12:54         ` Marcel Holtmann
2005-11-07 14:12           ` Claudio Takahasi
2005-11-07 14:54             ` Johan Hedberg [this message]
2005-11-07 20:57               ` Marcel Holtmann
2005-11-07 21:57                 ` Johan Hedberg
2005-11-08 13:44                   ` Marcel Holtmann
2005-11-08 14:31                     ` Johan Hedberg
2005-11-08 14:44                       ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051107145430.GA12669@localhost.localdomain \
    --to=johan.hedberg@nokia.com \
    --cc=bluez-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).