Async DBusMessage reads using the C API

[Matthew Johnson]

On Tue, 1 Nov 2005, Havoc Pennington wrote:

> Well, you have to either block on *something* or you have to busy-loop
> or you have to exit (right? those are the only possible alternatives
> when you have no immediate processing to do...)
>
> I'd take a guess you mean you need to block on something else, so if you
> block on the dbus socket you'll become unresponsive to the something
> else. This is the problem a main loop is intended to solve (the main
> loop just being an abstraction of
> select()/poll()/WaitForMultipleObjects()) so you can block on multiple
> things at once.

Yeah, but a lot of things already have one of these, so don't want to
retrofit a glib or other mainloop, and just want to throw in a
non-blocking call. At this level in the API you really need to offer a
non-blocking as well as a blocking call.

Matt

-- 
Matthew Johnson
http://www.matthew.ath.cx/