IPC using D-Bus

1.0 References

[1] Software Architecture Document, Version 1.1 Revision 1.4, LiMo Foundation, 11 September 2007

2.0 Overview

LiMo Foundation Platform Release 1 uses D-Bus from freedesktop.org for interprocess communication (IPC). Architecturally, D-Bus has the following layers:
  • A library, libdbus, that allows two applications to connect to each other and exchange messages.
  • A message bus daemon executable, built on libdbus, that multiple applications can connect to. The daemon can route messages from one application to zero or more other applications.
  • Wrapper libraries or bindings based on particular application frameworks. For example, libdbus-glib and libdbus-qt. There are also bindings to languages such as Python. These wrapper libraries are the API most people should use, as they simplify the details of D-Bus programming. libdbus is intended to be a low-level backend for the higher level bindings. Much of the libdbus API is only useful for binding implementation.

3.0 Industry Standard

D-Bus 1.0.2
http://www.freedesktop.org/wiki/Software/dbus#head-ed92e8f84ae0374ae3a2e3f714c2eb0037a84868

4.0 External API Documents

http://dbus.freedesktop.org/doc/dbus-tutorial.html

5.0 Plug-in Extension Point Interface

None

6.0 Other Interfaces

None

7.0 Other Notes

The URL provided in 3.0 Industry Standard links to D-Bus 1.0.2 documentation and downloadable source code. Documentation for the most recent version of D-Bus may be found at http://dbus.freedesktop.org/doc/api/html/index.html

To generate Doxygen documentation for D-Bus version 1.0.2:

Generated on Mon Mar 31 01:01:00 2008 by  doxygen 1.5.4