thiago at kde.org
Sat May 26 01:08:50 PDT 2007
Steve Kreyer wrote:
>I have a question about the org.freedesktop.DBus.Introspectable
>interface. My object supports this interface by specifying it in the
>iface definition, and by implementing the Introspect method,
>but if I
>request the method on the DBus- self object, via "dbus-send
>--print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus
>org.freedesktop.DBus.Introspectable.Introspect", the returned string of
>my implementation of Introspect does not appear in the reply.
Well, that's because you're not talking to your program. If you send a
call to dbus-daemon, it's dbus-daemon that will reply.
What happens if you use --dest=<your-program> ?
>So should I understand the interface as a standard, so that if a
>controller wants to get information he requests
>org.freedesktop.DBus.Introspectable.Introspect on my object and get this
>information? Or has it some real functional meanings inside the
>implementation of the DBus self object?
>I hope you understand my concern ...
Well, no, I don't understand the questions. Please clarify.
The org.freedesktop.DBus.Introspectable interface is an interface like any
other. So it's a "contract" between caller and callee. Caller says "I
will implement these methods, all of them, and each will have these
parameters; each method or signal shall have this meaning".
Anyone can implement an interface.
But, no, libdbus-1 or the D-Bus protocol do not assign any special meaning
to that interface. The only interface with special meaning is
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
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
Size: 189 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/dbus/attachments/20070526/a72d6f73/attachment.pgp
More information about the dbus