On Tue, 2010-03-09 at 09:39 +0000, Chen, Congwu wrote:
However, from server alerted sync view, this has some problem:
If the remote (The sync server) asks a "two-way" sync but SyncEvolution found
it cannot proceed without a "slow" sync, it aborts the sync process. However
from
the server side view, it cannot get any information on this failure and causing
confusion.
I think we may disable this feature if this is a server alerted sync at client side,
comments?
I agree, to some extend. The goal has to be that the initiator provides
the GUI and does this kind of checking. So if the initiator is
SyncEvolution running as server, it should do the checking. Currently
this doesn't work because we cannot detect slow syncs on the server side
(some necessary hooks missing).
The same thing happens when the initiator is some other software and
doesn't have the intelligent "slow sync" handling. Should SyncEvolution
offer the additional protection of not refusing a slow sync?
I think the answer is "yes", if the user asks for it explicitly. That
means that the default of "preventSlowSync" must depend on the context:
if server initiated, it is off, otherwise on.
--
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.