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: Tue, 8 Nov 2005 16:31:27 +0200 [thread overview]
Message-ID: <20051108143127.GA7773@localhost.localdomain> (raw)
In-Reply-To: <1131457496.5824.172.camel@blade>
Hi Marcel,
On Tue, Nov 08, 2005, Marcel Holtmann wrote:
> > 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.
>
> this might be too much work for the current interface. Or do you think
> it can be easily implemented?
It will require a moderate amount of coding, so it wont be easy at least
in that respect. However, I think that implementing D-BUS client
lifetime monitoring is a feature that we will inevitably have to
implement at some point anyway. It may e.g. be needed for noticing if a
program which requested an RFCOMM connection suddenly died (in which
case hcid/bluetoothd should disconnect that connection). Also, I've
already done it once (for dbus 0.23.4 though) for the D-BUS API we have
in maemo, so there shouldn't come any "supprises" when implementing it.
> > Ok, I'll begin by doing a patch for Inquiry and PeriodicInquiry
> > (probably during tomorrow).
>
> This would be great. For the next release I like to have the inquiry (or
> better name it device discovery) working. This will include some nice
> support for the extended inquiry. So you will get the remote name for
> free with a discovery. So is it possible to have different signatures
> for signals too?
Sure, and if the new signature differs only by having extra parameters
at the end it should even be backwards compatible (i.e.
dbus_message_get_args call for the old signature works also for the new
signature).
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
next prev parent reply other threads:[~2005-11-08 14:31 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
2005-11-08 13:44 ` Marcel Holtmann
2005-11-08 14:31 ` Johan Hedberg [this message]
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=20051108143127.GA7773@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).