[go: nahoru, domu]

D-Bus: Difference between revisions

Content deleted Content added
Un1Gfn (talk | contribs)
mNo edit summary
Line 146:
One of the earlier adopters was the (nowadays deprecated) [[HAL (software)|Hardware Abstraction Layer]]. HAL used D-Bus to export information about hardware that has been added to or removed from the computer.{{r|Palmieri 2005}}
 
The usage of D-Bus is steadily expanding beyond the initial scope of desktop environments to cover an increasing amount of system services. For instance, [[NetworkManager]] network daemon, [[BlueZ]] bluetooth stack and [[PulseaudioPulseAudio]] sound server use D-Bus to provide part or all of its services. [[systemd]] uses the D-Bus wire protocol for communication between [[Systemd#Core_components_and_libraries|{{mono|systemctl}}]] and systemd, and is also promoting traditional system daemons to D-Bus services, such as [[logind]].{{r|Poettering 2015 q2}} Another heavy user of D-Bus is [[Polkit]], whose policy authority daemon is implemented as a service connected to the system bus.{{r|polkit doc}}
 
It is also used as the [[Wire protocol]] for the [[AllJoyn]] protocol for [[home automation]], to this end AllJoyn adds discovery, session management, security, header compression, embedded device support and makes it transport agnostic.<ref>{{cite web|url=https://allseenalliance.org/developer-resources/forum/developers/difference-d-bus |title=Archived copy |accessdate=2015-06-16 |url-status=dead |archiveurl=https://web.archive.org/web/20150721005141/https://allseenalliance.org/developer-resources/forum/developers/difference-d-bus |archivedate=2015-07-21 }}</ref>