python - using a signal not in introspection

[John (J5) Palmieri]

On Thu, 2007-04-26 at 10:08 -0400, Havoc Pennington wrote:
> 
> Thiago Macieira wrote:
> > Havoc Pennington wrote:
> >> I did just think of a race with the client-side tracking approach:
> >>
> >>   AddMatch for first owner
> >>   new owner takes over
> >>   NameOwnerChanged emitted by bus
> >>   new owner emits signal
> >>   Signal dispatched by bus
> >>   Receive NameOwnerChanged with new owner
> >>   AddMatch for second owner
> > 
> > Don't use AddMatch for the first owner. Instead, use AddMatch for the name 
> > you're watching. The daemon handles that gracefully.
> 
> Yes, this is what I was saying dbus-python should do ;-) (and apparently 
> it does do now)

Now that I think of it the bug might have been in the bindings.  We
constructed a match tree in order to rout the message as fast as
possible on the client side.  It looks like it is working in the current
bindings but it may not work in 0.70.  I'm running 0.8x from OLPC on my
fc6 box.

-- 
John (J5) Palmieri <johnp at redhat.com>