On Fri, Jul 25, 2014 at 8:35 PM, Patrick Ohly <firstname.lastname@example.org> wrote:
On Fri, 2014-05-23 at 13:02 +0200, Patrick Ohly wrote:
Let's revive this mail thread once more. The goal is to agree on a
change of the README.rst, in particular in the terminology section, and
then make the necessary code changes to match that change.
I don't want to make code changes unless other developers or users agree
that the changes are an improvement, so please provide feedback.
I did like the new terminology. Its much better than previous one. Easy to understand. Also old terminology still works as fallback which is good.
One thing I always struggle, is to initiate a sync between two evolution databases defined in different contexts (without running syncevolution http server).
For example, lets say I have two calendars on evolution; Work & Personal. And they are defined like this (with new terminology):
syncevolution --configure --template none backend=evolution-calendar database=Work @Local workcal
syncevolution --configure --template none backend=evolution-calendar database=Personal @EDS personalcal
How to initiate a sync between them? Which one will act as client & which one as server?
Is it necessary to define them in different contexts(@Local, @EDS) at all? What if both are defined within @Local? Is it, then, possible to initiate a sync between them?