D-Bus is a message bus system, a simple way for applications to talk to one another. In addition to interprocess communication, D-Bus helps coordinate process lifecycle; it makes it simple and reliable to code a "single instance" application or daemon, and to launch applications and daemons on demand when their services are needed.
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 apps to communicate directly (without going through the message bus daemon). Currently the communicating applications are on one computer, or through unencrypted TCP/IP suitable for use behind a firewall with shared NFS home directories.
D-Bus is a message bus system, a simple way for applications to talk to one another. In addition to interprocess communication, D-Bus helps coordinate process lifecycle; it makes it simple and reliable to code a "single instance" application or daemon, and to launch applications and daemons on demand when their services are needed.
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 apps to communicate directly (without going through the message bus daemon). Currently the communicating applications are on one computer, or through unencrypted TCP/IP suitable for use behind a firewall with shared NFS home directories.
This is a Common Lisp library that publishes D-Bus objects as well as send and notify other objects connected to a bus.
This is a Common Lisp library that publishes D-Bus objects as well as send and notify other objects connected to a bus.
This package provides D-Bus client API bindings for the C++ programming language. It also provides the dbusxx-xml2cpp and dbusxx-introspect commands.
Dbus-cxx is a C++ wrapper for dbus.
It exposes the C API to allow direct manipulation and relies on sigc++ to provide an Oriented Object interface.
This package provide 2 utils:
dbus-cxx-xml2cppto generate proxy and adapterdbus-cxx-introspectto introspect a dbus interface
Some codes examples can be find at: https://dbus-cxx.github.io/examples.html
D-Bus is a simple, message-based protocol for inter-process communication, which allows applications to interact with other parts of the machine and the user's session using remote procedure calls. D-Bus is a essential part of the modern Linux desktop, where it replaces earlier protocols such as CORBA and DCOP. This library is an implementation of the D-Bus protocol in Haskell. It can be used to add D-Bus support to Haskell applications, without the awkward interfaces common to foreign bindings.
This package provides Rust bindings to D-Bus.
GLib bindings for D-Bus. The package is obsolete and superseded by GDBus included in Glib.
This is a Common Lisp library that publishes D-Bus objects as well as send and notify other objects connected to a bus.
python-dbus provides bindings for libdbus, the reference implementation of D-Bus.
python-dbus provides bindings for libdbus, the reference implementation of D-Bus.
This variant D-Bus package is built with verbose mode, which eases debugging of D-Bus services by printing various debug information when the DBUS_VERBOSE environment variable is set to 1. For more information, refer to the dbus-daemon(1) man page.
Net::DBus provides a Perl XS API to the DBus inter-application messaging system. The Perl API covers the core base level of the DBus APIs, not concerning itself yet with the GLib or QT wrappers.
D-Bus is a message bus system, a simple way for applications to talk to one another. In addition to interprocess communication, D-Bus helps coordinate process lifecycle; it makes it simple and reliable to code a "single instance" application or daemon, and to launch applications and daemons on demand when their services are needed.
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 apps to communicate directly (without going through the message bus daemon). Currently the communicating applications are on one computer, or through unencrypted TCP/IP suitable for use behind a firewall with shared NFS home directories.
This crate is a framework for writing D-Bus method handlers (legacy).
xdg-dbus-proxy is a filtering proxy for D-Bus connections. It can be used to create D-Bus sockets inside a Linux container that forwards requests to the host system, optionally with filters applied.
Access to D-Bus when using Rust's Tokio async framework.
python-dbusmock allows for the easy creation of mock objects on D-Bus. This is useful for writing tests for software which talks to D-Bus services such as upower, systemd, logind, gnome-session or others, and it is hard (or impossible without root privileges) to set the state of the real services to what you expect in your tests.
A small little utility to run a couple of executables under a new DBus session for testing.
This DBus library for Python aims to be a fully-featured high-level library primarily geared towards integration of applications into desktop and mobile environments.
This package provides Python bindings to libdbus, the reference implementation of the D-Bus protocol.
This package provides an extension to the Net::DBus module allowing integration with the GLib mainloop. To integrate with the main loop, simply get a connection to the bus via the methods in Net::DBus::GLib rather than the usual Net::DBus module. Every other API remains the same.
Framework for writing D-Bus method handlers in Rust.