Den 14. april 2014 09:36, skrev Patrick Ohly:
To do that, the original sync config's syncURL would no longer point to
a remote SyncML server, but, by using "local:", it can be set to point
to a local SyncML server within SyncEvolution itself, using a different
configuration context. For simplicity, that SyncML server is always
called "target-config", though it's otherwise just a completely normal
sync config, nothing special about it configuration-wise. It's just the
peer that SyncEvolution talks to internally when it's asked to talk to
itself.
Actually, the originating side acts as SyncML server and the
target-config as client, hence the "peerIsClient=1" in the originating
side.
Ah, I thought that option was for syncmode ("refresh-from-client" etc)
and things like that.
The property has to be set because at some point it might make
sense to allow reversing the roles. If that happens and configs are in
use where the property is not set, we wouldn't be able to use it.
So if you did, would that break "refresh-from-client/server"?
_______________________________________________
SyncEvolution mailing list
[email protected]
https://lists.syncevolution.org/mailman/listinfo/syncevolution
