On Mi, 2011-06-22 at 18:51 +0200, Ove Kaaven wrote:
Den 22. juni 2011 18:23, skrev Patrick Ohly:
>> How should I
>> determine which sources to ask SyncEvolution to create for the client
>> config? Is it possible to find out using --print-config?
> Yes, --print-config --template will tell you that. Note that for an
> existing context (like @default) it will include sources already
> configured inside that context.
Allright, but since I don't build from master, I'm not sure what that's
going to look like yet...
My hope is to have a 126.96.36.199 end of this week. This would be the 1.2
>> 2) Sync method
>> I suppose that syncURL, WebURL, username, password, and uri should go in
>> the server config, and database (evolutionsource) should go in the
>> client config. But when the user wants to set up a source for slow sync,
>> one-way sync etc, where should it go? Server config? Client config? Both?
> Careful with the naming here. I prefer "source" config for the side that
> talks to the server (source-config@yahoo) and "local" or "sync"
> for the side that is used for syncing (the one with local:// syncURL).
Yes, I've seen that you prefer that, but I don't, since "source
can be confused with "addressbook/calendar/etc config".
But "client" and "server" really aren't much better. Does it refer
the role of the config at the SyncML level or the server that it talks
to? It could be both.
I'm open for suggestions. We can still get it right for 1.2. Here are
1. sync config (used for syncing, contains the relevant "sync" mode
for sources) + target config (referenced by a sync config in
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
My personal preference is the first one. Does that get a majority? Shall
we rename the "source-config" to "target-config" then?
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.
> "database" is currently set automatically in the
source config (recent
> change on master). We still need to add support for listing the WebDAV
> resources that could be set here.
By "database" in the client config, I meant local storage (which local
calendar to sync with the remove side).
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
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.