From 151b3aaaeff42b76ecf4bd02aa28cda3ed98a501 Mon Sep 17 00:00:00 2001 From: Havoc Pennington Date: Tue, 7 Nov 2006 06:13:53 +0000 Subject: 2006-11-07 Havoc Pennington * 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). --- doc/dbus-specification.xml | 21 ++++++++++++++++----- 1 file changed, 16 insertions(+), 5 deletions(-) (limited to 'doc/dbus-specification.xml') 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 @@
D-Bus Specification - Version 0.11 - 6 February 2005 + Version 0.12 + 7 November 2006 Havoc @@ -114,9 +114,20 @@ 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. + + + + 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. + + + + 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. -- cgit