Re: [SyncEvolution] configuring local sync + ActiveSync + Evolution

Therefore I suggest to accept that sessions for config changes always lock the whole config tree, which allows that any config can be changed in such a session. This is an extension of the current D-Bus API and thus backwards compatible: * Session.SetConfig() modifies the config named in StartSession, as before * a new Session.SetNamedConfig(<config name>) modifies any config; it is only allowed in a session which was started with Server.StartSessionWithFlags(<config name>, ['no-sync']), where <config name> may be empty - such a session will prevent any other session from running, while normal sessions may one day run concurrently (not supported at the moment) * there is no need for a Session.GetNamedConfig() because Server.GetConfig() already provides that - should it be added anyway, for the sake of completeness?