Hello! FYI, here's a clarification for the config handling in the new D-Bus API.
commit f549ce9468fd7950845699f7b3db685941a0e325 Author: Patrick Ohly <[email protected]> Date: Fri Sep 11 12:26:33 2009 +0200 D-Bus API: unset property clarification Unset properties are not present in the configuration dictionaries at all. This is semantically different from set to empty string, which would be the alternative. A "None" or "NULL" string unfortunately doesn't exist in D-Bus (AFAIK). diff --git a/src/dbus/interfaces/syncevo-server-full.xml b/src/dbus/interfaces/syncevo-server-full.xml index f3bcd7a..cc8c91f 100644 --- a/src/dbus/interfaces/syncevo-server-full.xml +++ b/src/dbus/interfaces/syncevo-server-full.xml @@ -53,7 +53,15 @@ </arg> <arg type="a{sa{ss}}" name="configuration" direction="out"> <doc:doc><doc:summary>server (or template) configuration</doc:summary></doc:doc> - <doc:doc><doc:description>The dictionary keys are "source/<source name>" for sources and the empty string for the main + <doc:doc><doc:description>The dictionary keys are "source/<source name>" for sources and the empty string for the main + Properties which are not set are also not present in the + configuration dictionaries. The semantic difference between + "not set" and "empty" or "set to default" is that unset + values will always use the default value, even after that + changed during a software update. Properties that are set + always use the chosen value. + </doc:description> + </doc:doc> </arg> </method> _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
