[sync] Stripping UIDs

[Jan Schneider]

Zitat von Karsten Fourmont <fourmont at gmx.de>:

>> I'm actually going to move the complete import code into the  
>> applications' APIs, since SyncML is only a transportation protocol  
>> and doesn't know anything about the exchanged data.
>
> Basically I Good idea.
>
> But unfortunately the way exports and imports have to be done depend  
> on the individual device. So do we create device dependent export  
> flavors (like "export to vcalendar for Synthesis/Windows Mobile")?

That doesn't make much sense. OTOH it's still an option.

> For example Synthesis/Windows Mobile uses PRIORITY 1-3 while  
> Synthesis/Palm has something different. The standard says 1-9 and  
> horde uses 1-5. Similar for all day events: some devices expect  
> s.th. like
> DTSTART;FORMAT=DATE: 20061017
> while others can't deal with that and expect
> DTSTART: 20061017T000000
>
> The sad truth is: youu can't do an import of an icalendar 2.0 rfc  
> compliant event 100% right without knowing the device that produced  
> the entry. Same for the export. 95% maybe, but not 100%

This sucks, really. But looks like we have to deal with it.

> Fortunately SyncML _does_ know the device and also gets the DevInf  
> information with infos whhich attributes a devices expects and  
> supports. It uses this information in the device specific classes.  
> If we move this to the applications api we have to ensure that no  
> functionality gets lost.

One of the problems with *not* importing SIF data directly is, that we  
lose information because we convert into an intermediate format  
(iCalendar). Kronolith for example supports some event statuses that  
are compatible with Outlook but don't exist in the iCalendar standard.

>> might become handy to be able to import and export SIF data without  
>> using SyncML.
> It might. On the other hand: The current releases of the sync4j  
> connectors start supporting VCALENDAR for contacts and events. I'm  
> not sure if we should put too much effort into supporting a  
> proprietary format that even its creators are moving away from.
> But we need it to get the outlook connector running.

Yes, I noticed this too. But guess what, the Funambol connectors still  
send the SIF mime type with the SyncML packets, even when actually  
sending iCalendar data. *sigh*

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/