After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 773483 - [RFE] rework NetworkManager usage of generated D-Bus bindings in core
[RFE] rework NetworkManager usage of generated D-Bus bindings in core
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks: nm-next
 
 
Reported: 2016-10-25 14:18 UTC by Thomas Haller
Modified: 2020-11-12 14:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Thomas Haller 2016-10-25 14:18:38 UTC 
NetworkManager (server-side) uses gdbus-codegen to generate bindings for the D-Bus interface. Then all objects exposed on D-Bus derive from NMExportedObject, which glues the code together.

I think, this approach brings a rather large overhead with it, both in code size and runtime performance.

It should be improved. I suspect getting rid of gdbus-codegen entirely (server-side) would be the best option.

It could be evaluated by first refactoring a simple type like NMWifiAP.
Comment 1 André Klapper 2020-11-12 14:26:08 UTC 
bugzilla.gnome.org is being shut down in favor of a GitLab instance. 
We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time.

If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/

Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).