| arg |
|
|
- |
| blocking |
|
|
- |
| blocking.rs |
Connections and proxies that make blocking method calls. |
20305 |
- |
| channel |
|
|
- |
| channel.rs |
Connection base / building block.
Contains some helper structs and traits common to all Connection types.- |
6782 |
- |
| error.rs |
|
6113 |
- |
| ffidisp |
|
|
- |
| ffidisp.rs |
A connection that uses FFI callbacks to dispatch messages.
This is the legacy design used up to 0.6.x. It is not recommended for new development. |
11345 |
- |
| filters.rs |
|
1722 |
- |
| lib.rs |
D-Bus bindings for Rust
[D-Bus](http://dbus.freedesktop.org/) is a message bus, and is mainly used in Linux
for communication between processes. It is present by default on almost every
Linux distribution out there, and runs in two instances - one per session, and one
system-wide.
In addition to the API documentation, which you're currently reading, you might want to
look in the examples directory, which contains many examples and some additional documents.
README.md also contains a few quick "getting started" examples (as well as information about
the `futures` and `no-string-validation` features).
In addition to this crate, there are some companion crates:
* dbus-tokio for integrating D-Bus with [Tokio](http://tokio.rs)
* dbus-codegen for generating code from D-Bus introspection data
* libdbus-sys contains the raw bindings to the C libdbus library. |
1919 |
- |
| message |
|
|
- |
| message.rs |
Contains structs and traits closely related to D-Bus messages. |
22428 |
- |
| methoddisp.rs |
|
44338 |
- |
| nonblock |
|
|
- |
| nonblock.rs |
Async version of connection.
This module requires the `futures` feature to be enabled.
Current status:
* Basic client functionality is up and running, i e, you can make method calls and
receive incoming messages (e g signals).
* As for server side code, you can use the `tree` module with this connection, but it does not
support async method handlers.
You're probably going to need a companion crate - dbus-tokio - for this connection to make sense.
(Although you can also just call read_write and process_all at regular intervals, and possibly
set a timeout handler.) |
22884 |
- |
| prop.rs |
Unfortunately org.freedesktop.DBus has no properties we can use for testing, but PolicyKit should be around on most distros. |
5198 |
- |
| strings.rs |
This module contains strings with a specific format, such as a valid
Interface name, a valid Error name, etc.
(The internal representation of these strings are `Cow<str>`, but with a \0 byte
at the end to use it libdbus calls without extra allocations. This is usually nothing
you have to worry about.) |
7809 |
- |