From 83e41dff82abe99e1a35e70ca0bb60672204ffcd Mon Sep 17 00:00:00 2001 From: Havoc Pennington Date: Sat, 6 Sep 2003 21:12:11 +0000 Subject: 2003-09-06 Havoc Pennington * doc/dbus-specification.sgml: partial updates * bus/dbus-daemon-1.1.in: fix the config file docs for the zillionth time; hopefully I edited the right file this time. * bus/config-parser.c (append_rule_from_element): support send_type, send_path, receive_type, receive_path * bus/policy.c: add message type and path to the list of things that can be "firewalled" --- doc/dbus-specification.sgml | 53 ++++++++++++++++++++++++++++++--------------- 1 file changed, 35 insertions(+), 18 deletions(-) (limited to 'doc/dbus-specification.sgml') diff --git a/doc/dbus-specification.sgml b/doc/dbus-specification.sgml index 031bb329..7800165b 100644 --- a/doc/dbus-specification.sgml +++ b/doc/dbus-specification.sgml @@ -3,8 +3,8 @@
D-BUS Specification - Version 0.7 - 26 March 2003 + Version 0.8 + 06 September 2003 Havoc @@ -65,10 +65,10 @@ D-BUS is easy to use because it works in terms of messages rather than byte streams, and - does not require users to understand any complex concepts such as a - new type system or elaborate APIs. Libraries implementing D-BUS - may choose to abstract messages as "method calls" (see - ). + automatically handles a lot of the hard IPC issues. Also, the D-BUS + library is designed to be wrapped in a way that lets users use their + framework's existing object/type system, rather than learning a new + one specifically for IPC. @@ -83,11 +83,10 @@ forwards messages among them. - Things that D-BUS can be used for is for example notification of - system changes (notification of when a camera is plugged in to a - computer, or a new version of some software has been installed), - or desktop interoperablity, for example a file monitoring - service or a configuration service. + Uses of D-BUS include notification of system changes (notification of when + a camera is plugged in to a computer, or a new version of some software + has been installed), or desktop interoperablity, for example a file + monitoring service or a configuration service. @@ -279,9 +278,27 @@ - name + path STRING - The name of the message, such as org.freedesktop.Peer.Ping + The object to send the message to; objects are identified by + a path, "/foo/bar" + + + ifce + STRING + The interface to invoke a method call on, or + that a signal is emitted from. e.g. "org.freedesktop.Introspectable" + + + mebr + STRING + The member, either the method name or signal name. + e.g. "Frobate" + + + ernm + STRING + The name of the error that occurred, for errors rply @@ -298,10 +315,10 @@ . - sndr + sdrs STRING - The name of the base service that sent this message. - The message bus fills in this field; the field is + Sender service. The name of the base service that sent + this message. The message bus fills in this field; the field is only meaningful in combination with the message bus. @@ -480,9 +497,9 @@ Valid names - Messages and services have names with type STRING, meaning that + Services have names with type STRING, meaning that they must be valid UTF-8. However, there are also some - additional restrictions that apply to message and service names + additional restrictions that apply to service names specifically: They must contain at least one '.' (period) character -- cgit