From 6fcd97c08459243a00bf0b790da434cee6dade17 Mon Sep 17 00:00:00 2001 From: Havoc Pennington Date: Sun, 20 Aug 2006 21:41:42 +0000 Subject: 2006-08-20 Havoc Pennington * doc/dbus-faq.xml, doc/dbus-tutorial.xml: some improvements to the docs --- doc/dbus-faq.xml | 45 ++++++++++++++++++++++++--------------------- 1 file changed, 24 insertions(+), 21 deletions(-) (limited to 'doc/dbus-faq.xml') diff --git a/doc/dbus-faq.xml b/doc/dbus-faq.xml index 963db366..47072e9e 100644 --- a/doc/dbus-faq.xml +++ b/doc/dbus-faq.xml @@ -154,6 +154,26 @@ + + It helps to keep these concepts separate in your mind: + + + + Object/component system + + + + + GUI control/widget embedding interfaces + + + + + Interprocess communication system or wire protocol + + + + D-Bus is not a component system. "Component system" was originally defined by COM, and was essentially a workaround for the limitations @@ -177,7 +197,10 @@ in modern languages all objects are effectively "components." - A third, orthogonal feature is interprocess communication or IPC. + So components are fancy objects, and some objects are GUI controls. + + + A third, unrelated feature is interprocess communication or IPC. D-Bus is an IPC system. Given an object (or "component" if you must), you can expose the functionality of that object over an IPC system. Examples of IPC systems are DCOM, CORBA, SOAP, XML-RPC, and D-Bus. @@ -189,26 +212,6 @@ If you combine an IPC system with a set of GUI control interfaces, then you can have an out-of-process or dynamically-loaded GUI control. - - Summarizing, there are three orthogonal things: - - - - Object/component system - - - - - Control embedding interfaces - - - - - Interprocess communication system or wire protocol - - - - Another related concept is the plugin or extension. Generic plugin systems such as the -- cgit