Difference between revisions of "D-BUS"
(→Introduction to D-BUS) |
Weibullguy (talk | contribs) (Added description.) |
||
| Line 1: | Line 1: | ||
== Introduction to D-BUS == | == 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. | ||
== Sections of D-BUS == | == Sections of D-BUS == | ||
Revision as of 07:58, 17 January 2007
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.
