How to discover introspection toplevel objects
John (J5) Palmieri
johnp at redhat.com
Tue Jan 24 14:21:51 PST 2006
You should be able to call Introspect on the root object "/" on any
service that exports Introspect. Not sure if we actually implement it
that way, but we should.
On Tue, 2006-01-24 at 23:12 +0100, Kevin Krammer wrote:
> On Tuesday 24 January 2006 23:05, John (J5) Palmieri wrote:
> > On Tue, 2006-01-24 at 22:23 +0100, Kevin Krammer wrote:
> > > Hi,
> > >
> > > once an application knows an introspectable object is can look into the
> > > introspection data to find children.
> > >
> > > However I didn't find any documentation, or maybe I missed the relevant
> > > parts, on how to discover those "toplevel" objects.
> > >
> > > So, how should an application proceed if it wants to introspect an
> > > unknown peer application?
> > Read the specification
> > (http://dbus.freedesktop.org/doc/dbus-specification.html). There is a
> > method on the bus called org.freedesktop.DBus.ListNames.
> I am afraid this is a misunderstanding :)
> ListNames returns a list of applications or connections on the bus, right?
> I'll use an example:
> ListNames includes "org.freedesktop.DBus" for the bus itself, correct?
> Assuming that "/org/freedesktop/DBus" is introspectable (haven't checked) how
> would an application know about "/org/freedesktop/DBus"?
> Is this a default object that always exists in any connected application?
> dbus mailing list
> dbus at lists.freedesktop.org
John (J5) Palmieri <johnp at redhat.com>
More information about the dbus