Announcement

Collapse
No announcement yet.

D-Bus Broker Announced As A New, High Performance Message Bus

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • D-Bus Broker Announced As A New, High Performance Message Bus

    Phoronix: D-Bus Broker Announced As A New, High Performance Message Bus

    While BUS1 continues to be developed as a new in-kernel IPC mechanism following the failing of KDBUS, there is some new interesting D-Bus news in user-space. Linux developer David Herrmann has today announced the D-Bus Broker project...

    http://www.phoronix.com/scan.php?pag...x=D-Bus-Broker

  • #2
    Originally posted by GhostOfFunkS View Post
    Made by RH. Will be used by GNOME.
    Will probably break NetworkManager in KDE

    Comment


    • #3
      D-Bus cannot possibly make use of high performance capabilities because of inherent design limitations.
      From a client point of view, it uses a single connection with no internal locking or queuing. Therefore, the only robust way to communicate over DBus by running dispatcher in a single thread. Message rate will suffer regardless of how fast the server is.

      Getting rid of server hangs/crashes would be nice though.

      Comment


      • #4
        What about one DBUS for both kernel and user space or about bus1(kdbus) to dbus (broker) bridge?

        Comment


        • #5
          Originally posted by Peter Fodrek View Post
          What about one DBUS for both kernel and user space or about bus1(kdbus) to dbus (broker) bridge?
          D-Bus and bus1 integration is something we intend to explore in the future. But one step at a time

          Comment


          • #6
            Gotta love the open source community: not done with one bus in the kernel, already working on another

            Comment


            • #7
              another bus that will never land.

              Comment


              • #8
                Originally posted by cj.wijtmans View Post
                another bus that will never land.
                There is nothing to land. It is an independent user space implementation.

                Comment


                • #9
                  Originally posted by bug77 View Post
                  Gotta love the open source community: not done with one bus in the kernel, already working on another
                  I can understand why the nomenclature may be confusing. However, please note that bus1 is at the level of UDS (which dbus-daemon/dbus-broker are both currently built on top of). Ideally, we would get dbus-broker built on top of bus1 in order to show the benefits of bus1 over UDS, and hence help with its acceptance upstream. There is no duplication of work going on here.

                  Comment


                  • #10
                    Originally posted by cj.wijtmans View Post
                    another bus that will never land.
                    Buses don't fly.

                    Comment

                    Working...
                    X