Clarification on some bus behaviour

[Simon McVittie]

On Wed, 08 Sep 2010 at 12:12:58 +0100, Will Thompson wrote:
> On 08/09/10 10:56, Thiago Macieira wrote:
> >3) Is the application allowed to assume anything about the owner of the
> >org.freedesktop.DBus name?
> >
> >I think the answer here is No.
> >
> >The reference dbus-daemon has the owner of org.freedesktop.DBus as also
> >org.freedesktop.DBus, even though that's not a unique connection name.
> 
> I'm probably missing something, but I don't really see why you need
> to know who owns that bus name, if it's never going to change.
> 
> 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.

For what it's worth, dbus-python assumes the reference implementation's
behaviour. It classifies bus names into three categories: unique, well-known,
and bus daemon (which is usually treated as if it was unique).

    S