| Ticket UUID: | 1fd9b87257ad22cd6ab86d993f7bc243f85f0b68 | |||
| Title: | Add D-Bus implementation | |||
| Status: | Closed | Type: | Feature Request | |
| Severity: | Minor | Priority: | Low | |
| Subsystem: | Resolution: | Overcome By Events | ||
| Last Modified: | 2024-09-29 09:01:27 | |||
| Version Found In: | Milestone: | |||
| User Comments: | ||||
|
js added on 2024-01-27 10:41:06:
D-Bus is used for more and more things. It probably makes sense to add a D-Bus implementation. letterus added on 2024-01-27 20:11:27: Maybe it's interesting to have a native implementation. But keep in mind ObjGTK will generate wrappers for GLib's GIO library which has an high level API for DBus. So it could be worth to watch out for improving that one. Unreleased ObjGTK GIO Wrappers, OGDBus* classes. js added on 2024-06-01 13:22:24: Given more and more things on Linux require D-Bus these days (e.g. in order to discover the path of a device, as that is handled by systemd these days), a D-Bus implementation should probably be part of ObjFW itself and not limited to GTK applications using ObjFW. js added on 2024-09-29 09:01:27: With systemd moving to Varlink (which would be extremely trivial to implement in ObjFW), it might not make sense anymore to implement D-Bus in ObjFW. I'll close this bug for now. | ||||