9:23 a.m.
[copying the list with Ove's permission]
On Di, 2011-06-21 at 22:45 +0200, Ove Kaaven wrote:
So I'm trying to update the Maemo GUI to take these DAV setups
into
account, and it's getting a bit complicated. I've got a couple of
questions, and it's a bit hard to find the answers elsewhere (plus I
haven't compiled anything newer than 1.1.99.4), so I'll ask you...
1) Creation of a configuration from template
The webdav/README says that you should specify the sources you plan to
use, and apparently in both server and client configs. Now, assuming
you're going to add a Google Calendar and Yahoo template for the server
config, do I still need to specify which sources to create?
Depends. These templates are now in the master branch and they are set
up so that the Google templates only has "addressbook" as source and
Yahoo has "addressbook" + "calendar", but "addressbook"
disabled.
So you can create the source-config@yahoo like this:
syncevolution --configure --template yahoo source-config@yahoo
Because the template is deduced from the context name @yahoo,
this shortcut also works:
syncevolution --configure source-config@yahoo.
But then creating the local sync config "yahoo" has to check which
sources really work.
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.
But because the source-config configs are to be used inside their own
context, that won't happen in this case.
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"
config
for the side that is used for syncing (the one with local:// syncURL).
With these names, the real, remote syncURL goes into the "source-config"
where it can be used for command line operations like
list/import/export/modify items. Username and password should be set in
that same config, because these operations need them.
uri hardly ever needs to be changed. Just use the default
"addressbook/calendar/todo/memo".
"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.
"database" and "backend" in the local config is the same as for
SyncML.
In fact, it comes from the @default source configs and is shared between
all peer configs (including SyncML) defined in that context.
--
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.
9:51 a.m.
New subject: [SyncEvolution] Couple of questions about SyncEvolution configuration
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...
> 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"
config
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 config"
can be confused with "addressbook/calendar/etc config". (Besides,
webdav/README says the local config should use the "SyncEvolution
Client" template, which might also justify calling it client config.)
"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?
Thanks,
Ove
11:52 a.m.
New subject: [SyncEvolution] Couple of questions about SyncEvolution configuration
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 1.1.99.5 end of this week. This would be the 1.2
release candidate.
>> 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"
config
> 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
config"
can be confused with "addressbook/calendar/etc config".
Ack.
But "client" and "server" really aren't much better. Does it refer
to
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
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)
My personal preference is the first one. Does that get a majority? Shall
we rename the "source-config" to "target-config" then?
(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.
> "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
"sync/local" config.
--
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.
9:56 a.m.
New subject: [SyncEvolution] Couple of questions about SyncEvolution configuration
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". But I
suppose "sync" and "target" would work too.
> (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...
> 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). And, of course, not
tested against what syncevolution 1.2 is going to be...
Thanks,
Ove
11:37 a.m.
New subject: [SyncEvolution] Couple of questions about SyncEvolution configuration
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.
6:50 p.m.
New subject: [SyncEvolution] source-config@foo => target-config@foo (was: Re: Couple of questions about SyncEvolution configuration)
On Fri, 2011-06-24 at 20:37 +0200, Patrick Ohly wrote:
> > 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"?
Let's do it... done. Note the typo above: the expected config name is
now "target-config@<context>".
commit 8032247a5a004303cac5969b76a126b98fa298ef
Author: Patrick Ohly <patrick.ohly(a)intel.com>
Date: Tue Jun 28 18:42:43 2011 -0700
local sync: renamed "source-config" to "target-config"
As discussed on the mailing list, "source-config" is ambiguous because
the "addressbook/calendar/..." configs are also called "source
configs".
Now the naming is "sync" config (for the config with syncURL=local://,
because it is used for syncing) and "target" config (because it is
used as target in a sync config's syncURL).
Rejected:
"local" config - because the databases are not necessarily local
"source" config - see above
"client" or "server" config - because both sides might use local
data
and/or client/server could refer to the role
of the peer or the SyncML client/server model
used internally
--
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.
3409
days inactive
3416
days old
syncevolution@synevolution.org
5 comments
3 participants
participants (3)
-
Ove Kaaven -
Ove Kåven
-
Patrick Ohly