Question about asynchronous server. about dbus-rs HOT 7 CLOSED

It's possible to have one thread listen and receive D-Bus calls and another thread handle them.

Your D-Bus thread would look like this (rough outline) :

for item in connection.iter() {
    if let MethodCall(m) = item {
        channel.send(m);
        let reply = other_channel.recv();
        for r in reply { connection.send(r); }
    }
}

The main thread can either have a Tree, and handling is then done by calling Tree.handle() and the result back on the channel, or you can handle the message manually by calling methods on the message to figure out what message it is, and construct an appropriate reply using message.method_return().append(/* ... *).

Edit: minor fix to make example work with tree.handle()

from dbus-rs.

Could you elaborate a little on the Tree way please?

from dbus-rs.

You would set up the Tree like in the server example but instead of calling tree.run your code would look like (rough outline, add proper error handling) :

loop {
     let msg = channel.recv();
     let reply = tree.handle(msg);
     other_channel.send(reply);
}

from dbus-rs.

Got another related question, how would I go about sending asynchronous signals?

Let's say I want to emit the signals directly from the main thread, is there a way to do it?

I was trying to put the Connection into an Arc but it's not Sync and Send and share the Arc<tree::Signal> between the tree thread and the main thread, but I guess it wouldn't really work.

Any hints?

from dbus-rs.

The easiest way is to have two connections. I could see if I could make Connection Send, because I think it should be, but I doubt that will help much in your case.

There is also some stuff written about connection and thread safety in the API indicating that it could maybe even be Sync. That would require some work on my part though as my wrapper currently isn't sync.

from dbus-rs.

Won't the register_name explode because I'm overriding an already existing interface?

from dbus-rs.

Won't the register_name explode because I'm overriding an already existing interface?

You don't need to register a name to send signals, AFAIK?

from dbus-rs.