diff options
author | Havoc Pennington <hp@redhat.com> | 2006-11-07 06:13:53 +0000 |
---|---|---|
committer | Havoc Pennington <hp@redhat.com> | 2006-11-07 06:13:53 +0000 |
commit | 151b3aaaeff42b76ecf4bd02aa28cda3ed98a501 (patch) | |
tree | 88e435d7bf1c7450c358687cb02ae66f6f46a8d7 /doc/dbus-specification.xml | |
parent | 4c31ea9ee25282cf329e4b46eaa0454fd8a8256d (diff) |
2006-11-07 Havoc Pennington <hp@redhat.com>
* doc/dbus-specification.xml, doc/dbus-faq.xml, README: various
documentation updates. Bump faq/spec versions (not to 1.0; I don't
think the spec will be "finished"/1.0 when we ship the 1.0 library).
Diffstat (limited to 'doc/dbus-specification.xml')
-rw-r--r-- | doc/dbus-specification.xml | 21 |
1 files changed, 16 insertions, 5 deletions
diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml index 1e4ac4f5..e1b02f38 100644 --- a/doc/dbus-specification.xml +++ b/doc/dbus-specification.xml @@ -7,8 +7,8 @@ <article id="index"> <articleinfo> <title>D-Bus Specification</title> - <releaseinfo>Version 0.11</releaseinfo> - <date>6 February 2005</date> + <releaseinfo>Version 0.12</releaseinfo> + <date>7 November 2006</date> <authorgroup> <author> <firstname>Havoc</firstname> @@ -114,9 +114,20 @@ </itemizedlist> D-Bus is not intended to be a generic IPC system for any possible application, and intentionally omits many features found in other - IPC systems for this reason. D-Bus may turn out to be useful - in unanticipated applications, but future versions of this - spec and the reference implementation probably will not + IPC systems for this reason. + </para> + + <para> + At the same time, the bus daemons offer a number of features not found in + other IPC systems, such as single-owner "bus names" (similar to X + selections), on-demand startup of services, and security policies. + In many ways, these features are the primary motivation for developing + D-Bus; other systems would have sufficed if IPC were the only goal. + </para> + + <para> + D-Bus may turn out to be useful in unanticipated applications, but future + versions of this spec and the reference implementation probably will not incorporate features that interfere with the core use cases. </para> |