#d-bus #d-bus #ipc

dbus-crossroads

Framework for writing D-Bus method handlers

7 releases (4 breaking)

0.5.0 Sep 19, 2021
0.4.0 Jun 14, 2021
0.3.0 Oct 13, 2020
0.2.2 Aug 25, 2020
0.1.0 Jun 19, 2020

#11 in #d-bus

Download history 933/week @ 2022-03-11 1048/week @ 2022-03-18 941/week @ 2022-03-25 812/week @ 2022-04-01 749/week @ 2022-04-08 688/week @ 2022-04-15 843/week @ 2022-04-22 1148/week @ 2022-04-29 974/week @ 2022-05-06 1013/week @ 2022-05-13 952/week @ 2022-05-20 816/week @ 2022-05-27 1031/week @ 2022-06-03 991/week @ 2022-06-10 982/week @ 2022-06-17 1057/week @ 2022-06-24

4,208 downloads per month
Used in 15 crates (12 directly)

Apache-2.0/MIT

535KB
10K SLoC

crates.io API documentation license

dbus-crossroads is a library that helps you implement interfaces on object paths, i e "server side" method handler code.

It is not as mature as dbus::tree yet, but the API should be fairly stable and easier to use than dbus::tree. Go ahead and use it, and report any issues you find!

To get started, you can jump into the commented examples, one for sync one for async (dbus-tokio), and one slightly more advanced, or familiarize yourself using the API reference.

Design decisions (compared to dbus::tree):

  • First class support for both sync and async methods
  • Detect method arguments automatically through generics
  • ...but less generics in structs you use, which means less cluttered API
  • The tree/crossroads instance is Send (but not Sync).
  • You can now modify the instance from within a method handler
  • It is objects (paths) that can contain custom data, and they can contain different data for different objects
  • Interface descriptions are kept in a registry, which means less reference counting

Dependencies