From: Johan Hedberg <johan.hedberg@nokia.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] D-BUS fixes for hcid
Date: Wed, 16 Jun 2004 14:57:18 +0300 [thread overview]
Message-ID: <20040616115718.GA8420@kone> (raw)
In-Reply-To: <1087385828.4309.3.camel@pegasus>
On Wed, Jun 16, 2004, Marcel Holtmann wrote:
> since I don't know very much about D-Bus, please explain your changes to
> me. Why are they needed?
The first part with the error handling is needed because
dbus_pending_call_get_reply() may return NULL if a timeout occurs (a
reply isn't received in time). Also, if new errors are added in the
future it is probably better to check for the general case here:
dbus_message_get_type().
The second part (dbus_message_set_auto_activation) enables service
activation if the PinAgent service isn't aquired by any process (i.e.
the D-BUS daemon will execute the pin-helper program if needed).
> Don't get your point here, because it works perfect on my Debian Sid.
Do you mean that without these changes, the pin-helper is automatically
launched when a D-BUS message is sent by hcid to the service
org.bluez.PinAgent? I could not get it working without the changes. What
version of D-BUS are you using?
Johan
next prev parent reply other threads:[~2004-06-16 11:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 11:27 [Bluez-devel] D-BUS fixes for hcid Johan Hedberg
2004-06-16 11:37 ` Marcel Holtmann
2004-06-16 11:57 ` Johan Hedberg [this message]
2004-06-16 12:05 ` Johan Hedberg
2004-06-16 12:18 ` Marcel Holtmann
2004-06-16 12:45 ` Johan Hedberg
2004-06-16 13:06 ` Marcel Holtmann
2004-06-16 13:46 ` Johan Hedberg
2004-06-16 13:53 ` Marcel Holtmann
2004-06-16 13:58 ` Achim Bohnet
2004-06-16 14:18 ` Johan Hedberg
2004-06-16 23:06 ` Marcel Holtmann
2004-06-17 9:48 ` Johan Hedberg
2004-06-17 12:05 ` Marcel Holtmann
2004-06-17 7:27 ` Sjoerd Simons
2004-06-18 7:30 ` Achim Bohnet
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=20040616115718.GA8420@kone \
--to=johan.hedberg@nokia.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
/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.