Lines Matching refs:Bus
15 // Newer D-Bus services implement the Object Manager interface to inform other
60 // explicit ExampleClient::ExampleClient(dbus::Bus* bus)
61 // : bus_(bus),
71 // The D-Bus thread manager takes care of issuing the necessary call to
107 // obtain it from the object manager. Unlike the equivalent method on the bus
126 class Bus;
132 // ObjectManager implements both the D-Bus client components of the D-Bus
145 // D-Bus object identified by |object_path| and accessibile through
146 // |object_proxy|. The D-Bus interface name |interface_name| is that passed
158 // object has been added with the path |object_path|. The D-Bus interface
170 // object with the path |object_path| has been removed. Ths D-Bus interface
182 // Client code should use Bus::GetObjectManager() instead of this constructor.
183 ObjectManager(Bus* bus,
187 // Register a client implementation class |interface| for the given D-Bus
194 // Unregister the implementation class for the D-Bus interface named in
209 // the equivalent method on Bus this will return NULL if the object
222 // automatically called by the D-Bus thread manager, there should never be
227 // The Bus object will take care of this so you don't have to do it manually.
286 // D-Bus message in |reader|, which should consist of an dictionary mapping
292 // for the interface named |interface_name| using the D-Bus message in
317 Bus* bus_;
332 // against that object and a collection of D-Bus interface names and their
