From 76ee87af5b5007839012259304cce50a43e69638 Mon Sep 17 00:00:00 2001 From: Havoc Pennington Date: Sun, 23 Jan 2005 00:28:41 +0000 Subject: the new tutorial/FAQ --- doc/dbus-tutorial.xml | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-) (limited to 'doc/dbus-tutorial.xml') diff --git a/doc/dbus-tutorial.xml b/doc/dbus-tutorial.xml index ccb12d4c..6f5afc07 100644 --- a/doc/dbus-tutorial.xml +++ b/doc/dbus-tutorial.xml @@ -20,6 +20,10 @@ + + David + Wheeler + @@ -101,11 +105,16 @@ There are many, many technologies in the world that have "Inter-process communication" or "networking" in their stated purpose: MBUS, CORBA, DCE, COM/DCOM, DCOP, XML-RPC, SOAP, and probably hundreds - more. Each of these is tailored for particular kinds of application. + url="http://www.w3.org/TR/SOAP/">SOAP, MBUS, Internet Communications Engine (ICE), + and probably hundreds more. + Each of these is tailored for particular kinds of application. D-BUS is designed for two specific cases: @@ -130,7 +139,8 @@ have significant previous experience with different IPC solutions such as CORBA and DCOP. D-BUS is built on that experience and carefully tailored to meet the needs of these desktop projects - in particular. + in particular. D-BUS may or may not be appropriate for other + applications; the FAQ has some comparisons to other IPC systems. The problem solved by the systemwide or communication-with-the-OS case -- cgit