In computing, D-Bus is a message-oriented middleware mechanism that allows communication between multiple processes running concurrently on the same machine.
| FactSnippet No. 1,633,781 |
12 Facts About D-Bus
1.
3.
D-Bus provides additional or simplifies existing functionality to the applications, including information-sharing, modularity and privilege separation.
| FactSnippet No. 1,633,783 |
4.
D-Bus can be used as a framework to integrate different components of a user application.
| FactSnippet No. 1,633,784 |
5.
That does not mean that D-Bus is somehow limited to OOP languages—in fact, the most used implementation is written in C, a procedural programming language.
| FactSnippet No. 1,633,785 |
6.
D-Bus specification defines a number of administrative bus operations to be performed using the object that resides in the bus name.
| FactSnippet No. 1,633,786 |
7.
D-Bus was conceived as a generic, high-level inter-process communication system.
| FactSnippet No. 1,633,787 |
8.
D-Bus messages are high-level discrete items that a process can send through the bus to another connected process.
| FactSnippet No. 1,633,788 |
9.
D-Bus was started in 2002 by Havoc Pennington, Alex Larsson and Anders Carlsson.
| FactSnippet No. 1,633,789 |
10.
Usage of D-Bus is steadily expanding beyond the initial scope of desktop environments to cover an increasing amount of system services.
| FactSnippet No. 1,633,790 |
11.
The predominance of libdbus as the most used D-Bus implementation caused the terms "D-Bus" and "libdbus" to be often used interchangeably, leading to confusion.
| FactSnippet No. 1,633,791 |
12.
GDBus is an implementation of D-Bus based on GIO streams included in GLib, aiming to be used by GTK+ and GNOME.
| FactSnippet No. 1,633,792 |