On Fr, 2011-06-24 at 18:56 +0200, Ove Kåven wrote: > On 06/22/2011 08:52 PM, Patrick Ohly wrote: > > I'm open for suggestions. We can still get it right for 1.2. Here are > > some options: > > > > 1. sync config (used for syncing, contains the relevant "sync" mode > > for sources) + target config (referenced by a sync config in > > local:// syncURL) > > 2. local config (uses local databases) + target config (referenced > > by a sync config in local:// syncURL) > > 3. sync config (used for syncing) + source config (use for > > accessing the sources) > > 4. client config (uses templates for clients) + server config > > (accesses the server) > > 5. server config (acts as SyncML server) + client config (SyncML > > client) > > I've thought of them as "local config" and "remote config".
That makes sense only for a subset of the use cases. "local sync" was already used to synchronize between EDS (in the sync config) and files (in the target config), in which case "remote config" doesn't quite fit. > But I > suppose "sync" and "target" would work too. Okay. Given that we seem to settle on "sync" and "target", should we go all the way and not only use these terms in the configuration, but also in the actual config names? In other words, replace "source-config@foo" with "target@foo"? > >> (Besides, > >> webdav/README says the local config should use the "SyncEvolution > >> Client" template, which might also justify calling it client config.) > > > > That a client template is used here is a technical detail that might > > change at some point. > > I hope not, since then the GUIs would need to be changed again... The current way of setting it up certainly will continue to work. What I meant is that in addition, the roles might get swapped so that PeerIsClient may be false in the sync config. Currently this is not supported, but because it is required to set this correctly in the config, it will be possible to add the other mode in the future, should the need ever arise. > >> Anyway, you didn't answer my actual question: for configuring slow sync, > >> one-way sync, or disabling sync, where should the "sync" configuration > >> go? Server/source config? Client/local config? Both? > > > > Sorry, missed that part. The "sync" property needs to be set in the > > "sync/local" config. > > OK. > > I guess my updated GUI is pretty much ready - apart from not being sure > if I'm going to need to handle config migration somehow (like put up a > prompt that launches syncevolution --migrate). No need for that. A stable version will migrate automatically. You can emulate that by configuring with --enable-release-mode. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
