Question: why empty introspeciton files from org.freedesktop.Notifications and the like ? Repository of org.freedesktop introspection files available ?

[Simon McVittie]

On Sun, 17 Jul 2011 at 13:13:58 +0200, rony wrote:
> Still another question: are there general rules whether a "default
> object path" should exist and what the format of such a "default object
> path" should be, in the case that one cannot research/find out what the
> object path should be in order to call Introspect()?

Find the documentation for/definition of the D-Bus API you're using (in this
case org.freedesktop.Notifications), read it, it should specify how to find
the "entry point" object path. If not, then that API definition is incomplete
and you should complain to its bug tracker, assuming it has one.

Another way you could have found the right object path is: you might have
noticed that when you introspected "/", it indicated that it had a child node
called "org". If you introspect "/org", it will have a child node
"freedesktop". Carry on introspecting "/org/freedesktop", and so on, until you
reach an object path that has some more interesting methods.

(To do this in an automated way, you can use the GUI D-Bus debugging tool
"d-feet": it browses introspection data in exactly the same way.)

> [So far I had wrongly assumed a root path "/", but it could also be the
> case that the bus name is used, where the dots get replaced by slashes
> plus inserting a slash at the beginning of the object path.]

Using an object path corresponding to the bus name in this way is a popular
convention, but not guaranteed to be used.

Using '/' as an object path is usually a bad idea for the reasons Lennart and
Havoc describe here: <http://0pointer.de/blog/projects/versioning-dbus.html>
but some people use it anyway.

    S