Commit: 6aa1c4488ee96fd6a209b41b7148b037a888a783
Parent: 63c8fe7a4afb8e84c32a74b86934e49d0631584a
Author: Vinicius Costa Gomes <vcgomes@gmail.com>
Committer: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2016-05-04 17:50:28
Tree: e26f51c9876105e44637946a0cf440ded8a3214e

gdbus: Fix the ordering of signals Consider the following example: /foo properties: "A", "B" /bar properties: "C", "D" If during a given mainloop iteration, property "A" of object '/foo' is changed, then properties "C" and "D" of '/bar', lastly "B" of '/foo', the current code will emit the PropertiesChanged signals in following order: "A", "B", "C", "D". This may confuse applications that have a dependency on the order of those signals. This fixes the ordering, so in the example, the order becomes: "C", "D", "A", B". This is considered not to be a problem, as applications may use the flag G_DBUS_PROPERTY_CHANGED_FLAG_FLUSH, so property changed signals are emitted as soon as possible. The solution is for each object, to reschedule the signals every time a signal is emitted.

Diffstat

M gdbus/gdbus.h | 9 +++++++++
M gdbus/object.c | 12 ++++++++++- -

2 files changed, 19 insertions(+), 2 deletions(-)

View Full Diff | Patch