dbus_pending_call_set_notify race

[Alexander Larsson]

On Thu, 2006-11-30 at 12:00 -0500, Havoc Pennington wrote:

> Of course this is pretty inconvenient. Maybe instead of the idle 
> handler, we could offer a function that essentially did the above - "set 
> notify or return reply" - but even with that convenience function it's 
> annoying, since your notifier will be run in the main loop thread and 
> your set_notify_or_get_reply is in a different thread, and it's probably 
> a pain to code things in two ways so you can handle the reply in either 
> thread.

Yeah, the best thing would be handling it internally in dbus with an
idle.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Alexander Larsson                                            Red Hat, Inc 
                   alexl at redhat.com    alla at lysator.liu.se 
He's a maverick guitar-strumming shaman looking for 'the Big One.' She's a 
sarcastic extravagent safe cracker from beyond the grave. They fight crime!