On Thu, Apr 3, 2014 at 8:33 PM, Patrick Ohly <[email protected]> wrote:
> > Interesting. Maybe this is close to the root of my problem, because I
> > don't understand how "a property set in a sync config" and a property
> > set for a sync peer" are different. I will need to think about this
> > when I have a bit more time.
>
> With the current definition and implementation, sync properties are
> independent of any particular source and thus can be addressed by just
> giving the sync config ("foo@bar"). Source properties must be attached
> to a source and thus require a source name when accessing them ("foo@bar
> addressbook" for per-peer source properties, "@bar addressbook" for
> shared source properties).
>
>
I'm trying to follow all this, but even with the list of definitions in
hand, it only gets more rather than less cloudy for me. I'd really love to
work out just a single case (see: "Getting the concepts clear") and to
label all the concepts as the case develops. That way we have something
concrete to point to when there's confusion about definitions or their
application (which are not the same thing).
Sorry to harp on about this, but you guys are already deep into the
material, so these definitions have meaning for you *beyond* what's written
down; I'm trying to figure out what these concepts mean from how these
concepts are applied, and I'm getting fully stuck. If someone could just
work me through that one sample, not so much to get it working but as an
example of how and where to apply these concepts, that could be a launching
board for me to start describing their meaning (in context).
Emile
_______________________________________________
SyncEvolution mailing list
[email protected]
https://lists.syncevolution.org/mailman/listinfo/syncevolution
