All of lore.kernel.org
 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 23:57:32 +0200	[thread overview]
Message-ID: <20051107215732.GA19351@localhost.localdomain> (raw)
In-Reply-To: <1131397067.5824.145.camel@blade>

Hi Marcel,

On Mon, Nov 07, 2005, Marcel Holtmann wrote:
> > > 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.
> 
> I don't think so, because this options might be used not very often and
> so having them per unix user doesn't help. Two different applications
> running as them same user might have different needs. One wants to do
> inquiry with another IAC, the other with the general IAC. This tends to
> be a race condition.

Ok, I see your point. I didn't quite understand the use-case you were
thinking of earlier. One extra requirement that the dbus-id settings has
is that we will have to monitor the lifetime of a D-BUS client (by
listening NameOwnerChanged D-BUS signals) and remove the corresponding
entry from the settings table when an id gets removed from the bus.

> > 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.
> 
> Let's do this proposal first.

Ok, I'll begin by doing a patch for Inquiry and PeriodicInquiry
(probably during tomorrow).

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 21:57 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
2005-11-07 20:57               ` Marcel Holtmann
2005-11-07 21:57                 ` Johan Hedberg [this message]
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=20051107215732.GA19351@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.