-
Notifications
You must be signed in to change notification settings - Fork 25
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
Support file descriptor with Gio::UnixFDList #95
Comments
In case someone wants to contribute a patch, the main file that will have to be modified is dbustypes.py. I don't understand, though, why an annotation is needed. The file descriptors have their own signature ( |
I also wonder why gdbus supports file descriptors with annotation and GUnixFDList, not the dbustype 'h'. In my opinion, glib(gdbus) supports multiple OS platforms, unlike libdbus. So it seems to separate what is supported on UNIX platforms such as FD passing. |
I am not sure why the annotation was originally added (https://gitlab.gnome.org/GNOME/glib/commit/c404dbed11bc8bf4212d15719ef3a87ebf76efff in GLib does not say), but behavior in I do not see why an annotation would be needed for |
That |
Thank you for the detailed explanation. |
One gets all fd:s in a single |
Before the commit(https://gitlab.gnome.org/GNOME/glib/commit/e3f80b925405359ed70530f5a478d0e70ed78a4d ) was applied, GUnixFDList was not related to arguments. I haven't tried the latest glib version yet, so I'm not sure how 'h' works with GUnixFDList. However, this is a very interesting topic. I am wondering what will be the index of the GUnixFDList and the index of the 'h' arguments, assuming the method below.
|
gdbus-codegen supports file descriptors as the following anntation and GUnixFDList.
<annotation name = "org.gtk.GDBus.C.UnixFD" value = "true" />
It would be nice if gdbus-codegen-glibmm also supports file descriptors with the same annotation and Gio::UnixFDList.
I'm using glibmm's low API because the generator doesn't support it right now, so the code is unnatural.
The text was updated successfully, but these errors were encountered: