dbus/doc dbus-specification.xml,1.30,1.31 dbus-faq.xml,1.3,1.4
Colin Walters
walters at freedesktop.org
Thu Feb 17 13:19:51 PST 2005
Update of /cvs/dbus/dbus/doc
In directory gabe:/tmp/cvs-serv12542/doc
Modified Files:
dbus-specification.xml dbus-faq.xml
Log Message:
2005-02-17 Colin Walters <walters at verbum.org>
* dbus/dbus-protocol.h (DBUS_SERVICE_ORG_FREEDESKTOP_DBUS):
Rename to DBUS_SERVICE_DBUS.
(DBUS_PATH_ORG_FREEDESKTOP_DBUS): Rename to DBUS_PATH_DBUS.
(DBUS_PATH_ORG_FREEDESKTOP_LOCAL): Rename to DBUS_PATH_LOCAL.
(DBUS_INTERFACE_ORG_FREEDESKTOP_DBUS): Rename to DBUS_INTERFACE_DBUS.
(DBUS_INTERFACE_ORG_FREEDESKTOP_INTROSPECTABLE): Rename to
DBUS_INTERFACE_INTROSPECTABLE.
(DBUS_INTERFACE_ORG_FREEDESKTOP_PROPERTIES): Rename to
DBUS_INTERFACE_PROPERTIES.
(DBUS_INTERFACE_ORG_FREEDESKTOP_PEER): Rename to
DBUS_INTERFACE_PEER.
(DBUS_INTERFACE_ORG_FREEDESKTOP_LOCAL):
DBUS_INTERFACE_LOCAL.
All other users of those constants have been changed.
* bus/driver.c (bus_driver_handle_introspect): Use constants.
* glib/dbus-gobject.c (handle_introspect): Use constants.
* doc/dbus-faq.xml, doc/dbus-specification.xml: Update for rename.
Index: dbus-specification.xml
===================================================================
RCS file: /cvs/dbus/dbus/doc/dbus-specification.xml,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -d -r1.30 -r1.31
--- dbus-specification.xml 17 Feb 2005 21:11:18 -0000 1.30
+++ dbus-specification.xml 17 Feb 2005 21:19:49 -0000 1.31
@@ -2208,17 +2208,17 @@
that may be useful across various D-BUS applications.
</para>
<sect2 id="standard-interfaces-peer">
- <title><literal>org.freedesktop.Peer</literal></title>
+ <title><literal>org.freedesktop.DBus.Peer</literal></title>
<para>
- The <literal>org.freedesktop.Peer</literal> interface
+ The <literal>org.freedesktop.DBus.Peer</literal> interface
has one method:
<programlisting>
- org.freedesktop.Peer.Ping ()
+ org.freedesktop.DBus.Peer.Ping ()
</programlisting>
</para>
<para>
On receipt of the <literal>METHOD_CALL</literal> message
- <literal>org.freedesktop.Peer.Ping</literal>, an application should do
+ <literal>org.freedesktop.DBus.Peer.Ping</literal>, an application should do
nothing other than reply with a <literal>METHOD_RETURN</literal> as
usual. It does not matter which object path a ping is sent to. The
reference implementation should simply handle this method on behalf of
@@ -2228,11 +2228,11 @@
</sect2>
<sect2 id="standard-interfaces-introspectable">
- <title><literal>org.freedesktop.Introspectable</literal></title>
+ <title><literal>org.freedesktop.DBus.Introspectable</literal></title>
<para>
This interface has one method:
<programlisting>
- org.freedesktop.Introspectable.Introspect (out STRING xml_data)
+ org.freedesktop.DBus.Introspectable.Introspect (out STRING xml_data)
</programlisting>
</para>
<para>
@@ -2246,25 +2246,25 @@
</para>
</sect2>
<sect2 id="standard-interfaces-properties">
- <title><literal>org.freedesktop.Properties</literal></title>
+ <title><literal>org.freedesktop.DBus.Properties</literal></title>
<para>
Many native APIs will have a concept of object <firstterm>properties</firstterm>
or <firstterm>attributes</firstterm>. These can be exposed via the
- <literal>org.freedesktop.Properties</literal> interface.
+ <literal>org.freedesktop.DBus.Properties</literal> interface.
</para>
<para>
<programlisting>
- org.freedesktop.Properties.Get (in STRING interface_name,
- in STRING property_name,
- out VARIANT value);
- org.freedesktop.Properties.Set (in STRING interface_name,
- in STRING property_name,
- in VARIANT value);
+ org.freedesktop.DBus.Properties.Get (in STRING interface_name,
+ in STRING property_name,
+ out VARIANT value);
+ org.freedesktop.DBus.Properties.Set (in STRING interface_name,
+ in STRING property_name,
+ in VARIANT value);
</programlisting>
</para>
<para>
The available properties and whether they are writable can be determined
- by calling <literal>org.freedesktop.Introspectable.Introspect</literal>,
+ by calling <literal>org.freedesktop.DBus.Introspectable.Introspect</literal>,
see <xref linkend="standard-interfaces-introspectable"/>.
</para>
<para>
@@ -2460,14 +2460,14 @@
<literal>DESTINATION</literal> field is absent, the call is taken to be
a standard one-to-one message and interpreted by the message bus
itself. For example, sending an
- <literal>org.freedesktop.Peer.Ping</literal> message with no
+ <literal>org.freedesktop.DBus.Peer.Ping</literal> message with no
<literal>DESTINATION</literal> will cause the message bus itself to
reply to the ping immediately; the message bus will not make this
message visible to other applications.
</para>
<para>
- Continuing the <literal>org.freedesktop.Peer.Ping</literal> example, if
+ Continuing the <literal>org.freedesktop.DBus.Peer.Ping</literal> example, if
the ping message were sent with a <literal>DESTINATION</literal> name of
<literal>com.yoyodyne.Screensaver</literal>, then the ping would be
forwarded, and the Yoyodyne Corporation screensaver application would be
Index: dbus-faq.xml
===================================================================
RCS file: /cvs/dbus/dbus/doc/dbus-faq.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- dbus-faq.xml 23 Jan 2005 03:53:34 -0000 1.3
+++ dbus-faq.xml 17 Feb 2005 21:19:49 -0000 1.4
@@ -123,7 +123,7 @@
generic <literal>TextEditor</literal>), have multiple objects (maybe
<literal>/org/kde/documents/4352</literal> where the number changes
according to the document), and each object could implement multiple
- interfaces, such as <literal>org.freedesktop.Introspectable</literal>,
+ interfaces, such as <literal>org.freedesktop.DBus.Introspectable</literal>,
<literal>org.freedesktop.BasicTextField</literal>,
<literal>org.kde.RichTextDocument</literal>.
</para>
More information about the dbus-commit
mailing list