Difference between revisions of "D-BUS"

From CBLFS
Jump to navigationJump to search
 
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Introduction to D-BUS ==
+
{{Package-Introduction|D-BUS is an inter-process communication (IPC) system.  D-BUS allows programs to register, offering services to other programs. Client programs are provided the opportunity to "look up" which services are available.
  
D-BUS is a message bus system, a simple way for applications to talk to one another. D-BUS supplies both a system daemon (for events such as “new hardware device added” or “printer queue changed”) and a per-user-login-session daemon (for general IPC needs among user applications). Also, the message bus is built on top of a general one-to-one message passing framework, which can be used by any two applications to communicate directly (without going through the message bus daemon).
+
Users can run several channels of D-BUS since D-BUS is implemented as a daemon. Usually there is a system channel and a private channel for each logged user. The primary mission of the system channel is to deliver signals from the HAL daemon to the processes interested in them. The mission of the private channels is to provide communication among the user's applications.
 +
 
 +
Each application that uses D-BUS contains objects, which map to GObject, QObject, or Python objects. The additional bindings are provided for these different types of objects.}}
  
 
== Sections of D-BUS ==
 
== Sections of D-BUS ==
Line 11: Line 13:
 
----
 
----
 
* [[Main Page]]
 
* [[Main Page]]
 +
 +
[[Category:General Utilities]]

Latest revision as of 14:53, 19 March 2009

Introduction to D-BUS

D-BUS is an inter-process communication (IPC) system. D-BUS allows programs to register, offering services to other programs. Client programs are provided the opportunity to "look up" which services are available.

Users can run several channels of D-BUS since D-BUS is implemented as a daemon. Usually there is a system channel and a private channel for each logged user. The primary mission of the system channel is to deliver signals from the HAL daemon to the processes interested in them. The mission of the private channels is to provide communication among the user's applications.

Each application that uses D-BUS contains objects, which map to GObject, QObject, or Python objects. The additional bindings are provided for these different types of objects.

Project Homepage: Unknown

Sections of D-BUS