Re: [Opensync-devel] akonadi-sync (discussion)

[deloptes <del...@ya...>]

deloptes wrote:

> I had a closer look into the discover funtion and I think it can do much
> more then mapping event obj and contact.

So I took advantage to add support for multiple collection.

The thing is that I have to run --discover after each --configure and I am
not sure if it is intended to work like this.

I think the discover should check if the engine supports the formats at the
opposite end, which I want to implement next, to avoid the second run of
discover.

The action plan for the sync is for what I believe that is rational and
pragmatic as following:

 1. --configure (optional, ATM mandatory)
 2. --discover  (mandatory)
 3. --configure (enable disable ressources)
 4. -- sync

So this is my goal, next

A. check for ressources and report syncs only if format is supported by the
other member(s) in the discover phase
B. Work the event/note/todo sync out
C. Check why todo is reporting XML validation error.

My question is why this is causing a problem in the sync

BEGIN:VCALENDAR
PRODID:-//K Desktop Environment//NONSGML libkcal 4.3//EN
VERSION:1.0
BEGIN:VTODO
DUE:20101201T000000
DCREATED:20100917T231809Z
UID:libkcal-1407423793.37
SEQUENCE:5
LAST-MODIFIED:20101010T215459Z
X-ORGANIZER:MAILTO:developer@lisa
SUMMARY:Finish the pluging
STATUS:NEEDS_ACTION
PRIORITY:5
END:VTODO

END:VCALENDAR

anyway, I'll look forward to understand how calendars are to be handled

regards