From freedesktop-dbus  Mon May 29 17:56:50 2006
From: Thiago Macieira <thiago.macieira () trolltech ! com>
Date: Mon, 29 May 2006 17:56:50 +0000
To: freedesktop-dbus
Subject: Re: dbus_connection_send_with_reply_and_block and unrelated messages
Message-Id: <200605291956.58094.thiago.macieira () trolltech ! com>
X-MARC-Message: https://marc.info/?l=freedesktop-dbus&m=117323264630647
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart6078488.r5hJBYQnVQ"

--nextPart6078488.r5hJBYQnVQ
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

William Lachance wrote:
>On 5/29/06, Kevin Krammer <kevin.krammer@gmx.at> wrote:
>> On Sunday 28 May 2006 15:22, Thiago Macieira wrote:
>> > The reason I'm asking is that I'm making a call to
>> > org.freedesktop.DBus.RequestName. Before the reply comes in, we get
>> > two signals. This means those two signals will be in the dispatcher
>> > queue. But the Qt bindings won't see them until there's activity
>> > again in the D-BUS socket.
>>
>> Another scenario is when you start an async call followed by a sync
>> call without returing to the eventloop inbetween.
>
>This reminds me of something I've been wondering about: is there any
>reason why dbus can't provide an async version of
>dbus_bus_request_name? Such a method would be useful to those of us
>who want to provide a high-level API which is purely non-blocking..

Quite frankly, I don't see the need.

Two reasons:
1) the call goes to the D-BUS server daemon. That should be reasonably=20
fast.

2) if you really need the async version, place your own call=20
asynchronously and wait for the reply with DBusPendingCal

=2D-=20
Thiago Jos=E9 Macieira - thiago.macieira AT trolltech.com
Trolltech AS - Sandakerveien 116, NO-0402 Oslo, Norway

--nextPart6078488.r5hJBYQnVQ
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQBEezXqM/XwBW70U1gRAu9IAKCoDXOfkj56oDmjql+fMDTthVi8TgCfbcOg
Ss2ah3wsjFzQGsWjMixwTz0=
=f957
-----END PGP SIGNATURE-----

--nextPart6078488.r5hJBYQnVQ--