diff options
| author | Lubomir Rintel <lkundrak@v3.sk> | 2016-10-18 16:35:07 +0200 |
|---|---|---|
| committer | Lubomir Rintel <lkundrak@v3.sk> | 2016-11-10 16:48:48 +0100 |
| commit | 97ce3964f1c9b1834dca2be319e1a932f66ce1cc (patch) | |
| tree | ff92cacbfccf0c1b1bb09ee397c515bcd6b90b5e /docs | |
| parent | 3adfdf5ccf2fd52e76ba991e928be0b415cf5c3e (diff) | |
libnm: use the o.fd.DBus.ObjectManager API for object management
This speeds up the initial object tree load significantly. Also, it
reduces the object management complexity by shifting the duties to
GDBusObjectManager.
The lifetime of all NMObjects is now managed by the NMClient via the
object manager. The NMClient creates the NMObjects for GDBus objects,
triggers the initialization and serves as an object registry (replaces
the nm-cache).
The ObjectManager uses the o.fd.DBus.ObjectManager API to learn of the
object creation, removal and property changes. It takes care of the
property changes so that we don't have to and lets us always see a
consistent object state. Thus at the time we learn of a new object we
already know its properties.
The NMObject unfortunately can't be made synchronously initializable as
the NMRemoteConnection's settings are not managed with standard
o.fd.DBus Properties and ObjectManager APIs and thus are not known to
the ObjectManager. Thus most of the asynchronous object property
changing code in nm-object.c is preserved. The objects notify the
properties that reference them of their initialization in from their
init_finish() methods, thus the asynchronously created objects are not
allowed to fail creation (or the dependees would wait forever). Not a
problem -- if a connection can't get its Settings, it's either invisible
or being removed (presumably we'd learn of the removal from the object
manager soon).
The NMObjects can't be created by the object manager itself, since we
can't determine the resulting object type in proxy_type() yet (we can't
tell from the name and can't access the interface list). Therefore the
GDBusObject is coupled with a NMObject later on.
Lastly, now that all the objects are managed by the object manager, the
NMRemoteSettings and NMManager go away when the daemon is stopped. The
complexity of dealing with calls to NMClient that would require any of
the resources that these objects manage (connection or device lists,
etc.) had to be moved to NMClient. The bright side is that his allows
for removal all of the daemon presence tracking from NMObject.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/libnm/Makefile.am | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/docs/libnm/Makefile.am b/docs/libnm/Makefile.am index f3f0cf7eb..1aae42f53 100644 --- a/docs/libnm/Makefile.am +++ b/docs/libnm/Makefile.am @@ -45,7 +45,6 @@ IGNORE_HFILES= \ nm-ip4-config.h \ nm-ip6-config.h \ nm-manager.h \ - nm-object-cache.h \ nm-object-private.h \ nm-property-compare.h \ nm-remote-connection-private.h \ |