Thomas Haller cdea5ca795 dispatcher: keep the GDBusConnection instance in the global variable ... It's anyway a singleton that is still referenced by other components. So unrefing it in the mainloop does not actually release any memory. However, the GDBusConnection singleton is fundamental for the run of the program. Keep it accessible in the global variables. Note that soon I will drop the GDBusInterfaceSkeleton and only operate on the GDBusConnection. Then it makes more sense to keep it around. Note that usually we want to keep the amount of global state small. But this connection is anyway a singleton (that we already implicitly use). So, it doesn't change the amount of global state nor does it really have much state (we either have a reference to the singleton or we don't).		2019-05-27 12:09:53 +02:00
..
tests	build/meson: rename "nm_core_dep" to "libnm_core_dep"	2019-04-18 20:13:49 +02:00
meson.build	build/meson: rename "nm_core_dep" to "libnm_core_dep"	2019-04-18 20:13:49 +02:00
nm-dispatcher-utils.c	shared: build helper "libnm-libnm-core-{intern|aux}.la" library for libnm-core	2019-04-18 20:07:44 +02:00
nm-dispatcher-utils.h	callouts/dispatcher: rename directory callouts	2016-10-13 21:33:33 +02:00
nm-dispatcher.c	dispatcher: keep the GDBusConnection instance in the global variable	2019-05-27 12:09:53 +02:00
nm-dispatcher.conf	callouts/dispatcher: rename directory callouts	2016-10-13 21:33:33 +02:00
nm-dispatcher.xml	callouts/dispatcher: rename directory callouts	2016-10-13 21:33:33 +02:00
org.freedesktop.nm_dispatcher.service.in	callouts/dispatcher: rename directory callouts	2016-10-13 21:33:33 +02:00