Re: [Opensync-devel] akonadi-sync phase 2

[Chris F. <cd...@fo...>]

On Sun, Jan 16, 2011 at 06:15:57PM +0100, deloptes wrote:
> The question was how to implement the check in akonadi because akonadi has a
> revision number which is incremented internally every time you edit the
> record. It has ID and RemoteID, so I was not sure what I should check. I'm
> still not sure the way I've implemented it  is the best one, but for the
> time and stage of development it is also satisfactory. The current solution
> uses RemoteID for change-id and the Revision for the hash (hash =
> RemoteID+"-"+Revision. I am not sure if I need to keep a tack of the
> akonadiId.

I don't use Akonadi, so I'm going purely on your description here, but
if the Revision number is always incremented every time an entry is edited,
and only then, then that is a perfectly good number to use for the hash.


> However I think this is only a problem when syncing akonadi with
> akonadi, because each of them increments Revision by 1 and on the next sync
> it reports change, but the content is the same.

Do you mean you are syncing the same akonadi with itself?  That would
cause problems, I guess.  But if you're syncing one akonadi with a
separate one, then how could the separate revision numbers be affected?
I smell the scent of a bug here, but I don't know enough to say if it's
just in my understanding. :-)

- Chris