| commit | 0b7fe6e2ac16f5cf99bee68ce2c82b13d5ed4fce | |
| author | Ryan Lortie <desrt@desrt.ca> | |
| Wed, 23 Jan 2013 23:06:02 +0000 (23 18:06 -0500) | ||
| committer | Ryan Lortie <desrt@desrt.ca> | |
| Thu, 24 Jan 2013 15:56:51 +0000 (24 10:56 -0500) | ||
| tree | bee7905f862bd8b9003bfd82a055b933de6c3b70 | treesnapshot (tar.gz zip) |
| parent | 5d7da8c59b3d8bea0fe0214602306629f8df13a9 | commitdiff |
engine: accept out-of-order error reply messages
Due to a quirk of the implementation of the D-Bus daemon (see upstream
bug https://bugs.freedesktop.org/show_bug.cgi?id=59780 for details)
error messages can arrive out of sequence with repsect to the order of
the method calls that they are in reply to.
This may or may not be a violation of the strict-ordering principle of
D-Bus (which does not actually appear to be written into the spec) but
either way, we should dial down our assumptions about ordering since the
D-Bus implementation that everyone is using does not currently work this
way.
https://bugzilla.gnome.org/show_bug.cgi?id=687120
Due to a quirk of the implementation of the D-Bus daemon (see upstream
bug https://bugs.freedesktop.org/show_bug.cgi?id=59780 for details)
error messages can arrive out of sequence with repsect to the order of
the method calls that they are in reply to.
This may or may not be a violation of the strict-ordering principle of
D-Bus (which does not actually appear to be written into the spec) but
either way, we should dial down our assumptions about ordering since the
D-Bus implementation that everyone is using does not currently work this
way.
https://bugzilla.gnome.org/show_bug.cgi?id=687120
| engine/dconf-engine.c | diffblobblamehistory |