The assumption is correct because a sync remains resumable only if no
other profile is synced in between (should be that way, see update
below). This is because the implementation cannot hold resume states
for more than one profile (e.g. the chgl_markedforresume flag would
need to be per profile).
Hi,
thanks for the patch to fix the client+statistics problem with
counting client adds as updates when the server returns 200 for them
instead of 201.
There is one basic problem with your solution: The fact that a entry
in the database already has a change log entry does NOT mean that
The reason for this is that the changelog is shared between multiple
profiles (multiple servers), and thus the changelog entries are
created when ANY of the profiles first sees the entry.
Ah, I now remember you have mentioned PRO version synthesis client
use multi-profiles sharing the same
