[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freedesktop-dbus
Subject:    Re: dbus_connection_send_with_reply_and_block and unrelated messages
From:       "William Lachance" <wrlach () gmail ! com>
Date:       2006-05-29 16:44:36
Message-ID: b78c39a60605290944id19334bq51f0d9a124094a78 () mail ! gmail ! com
[Download RAW message or body]

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..
--=20
William Lachance
wrlach@gmail.com

[prev in list] [next in list] [prev in thread] [next in thread]