Lines Matching full:manager
18 // Newer D-Bus services implement the Object Manager interface to inform other
26 // simplifying implementation, since there tends to be a single object manager
57 // The link between the implementation class and the object manager is set up
59 // a pointer to its object manager for use in other methods and establish
74 // The D-Bus thread manager takes care of issuing the necessary call to
77 // The object manager interface class has one abstract method that must be
101 // manager class handles that for you.
105 // interface or from the Object Manager interface. You may also wish to
110 // obtain it from the object manager. Unlike the equivalent method on the bus
119 // use of object manager behind the scenes, the rules for updating properties
136 // Object Manager interface, as internal methods, and a public API for
203 // to this manager.
207 // implementing the interface named in |interface_name| known to this manager.
213 // manager has not been informed of that object's existance.
217 // |interface_name|, or NULL if the object manager has not been informed of
224 // Instructs the object manager to refresh its list of managed objects;
225 // automatically called by the D-Bus thread manager, there should never be
314 // Removes all objects and interfaces from the object manager when
