Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plans for service-side APIs? #4

Open
mathstuf opened this issue Jul 26, 2015 · 3 comments
Open

Plans for service-side APIs? #4

mathstuf opened this issue Jul 26, 2015 · 3 comments

Comments

@mathstuf
Copy link
Contributor

It appears this is only for communicating over D-Bus, not for setting up a service on the bus.

Related, any plans for converting from an XML description to a Rust skeleton (c.f., qdbusxml2cpp from Qt)?

@srwalter
Copy link
Owner

You currently can create a service on the bus, just by receiving messages and processing them. Admittedly, that's a fairly low-level API, but it works well for simple cases.

We're looking at options for using e.g. macros to conveniently expose rust methods over D-Bus. Stay tuned for that :-)

@mathstuf
Copy link
Contributor Author

mathstuf commented Sep 1, 2015

FYI, I have this built on top of dbus-rs right now. Would like to move to a pure-Rust version at some point. I don't expect my approach is going to be very idiomatic, but feel free to take ideas :) . I may write tools to generate code from XML too; will have to see how messy the code gets.

@mathstuf
Copy link
Contributor Author

So I tried porting the ez-dbus library to dbus-bytestream, but the mut requirement to send a message seems to get in the way :( . It seems dbus-rs gets away with it by hiding all the mut behind the FFI and unsafe blocks :/ .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants