Clarification on some bus behaviour

Thiago Macieira thiago at
Wed Sep 8 05:47:43 PDT 2010

Em Quarta-feira 08 Setembro 2010, às 14:19:57, Will Thompson escreveu:
> On 08/09/10 13:02, Thiago Macieira wrote:
> > Thank you. I'd say apply the patch.
> Done. Time to figure out how to update the spec on the website.
> >> I guess you need to verify that incoming messages from the daemon really
> >> are from the daemon; but if so, I think it would be better for everyone
> >> if we mandated the reference implementation's behaviour.
> > 
> > I don't need to verify that incoming messages from the daemon are from
> > the daemon. I need a way of telling apart an incoming message from the
> > daemon from a message coming from somewhere else.
> > 
> > Each message has a sender field. I just need to know what to expect in
> > this field.
> Well, again this would be easier if the reference implementation's
> behaviour was mandatory, as dbus-python assumes it is.

Indeed, that would allow me to pre-populate the name owners cache with the 

Let's wait for other daemon implementors to chime in first.

Thiago Macieira - thiago (AT) - thiago (AT)
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <>

More information about the dbus mailing list