Comment 96 for bug 1439288

(In reply to André Miranda from comment #91)
> Now I wonder if this isn't a case for caching this property in order to
> avoid multiple (unnecessary) calls to dbus. Maybe Xfconf should handle this,
> if not each scenario has to be evaluated and the cache should be coded
> ad-hoc?(I guess the latter is kludge).

Xfconf has an internal cache, but dbus communication only work in the main loop, and since the io jobs run in a separate thread pool it is not suitable for outside communication / ui updates.

Just cache it in the structure and its ok.