[Tickets #7989] Re: Request: Support for task relations in SyncML

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7989
------------------------------------------------------------------------------
  Ticket             | 7989
  Updated By         | Jan Schneider <jan at horde.org>
  Summary            | Request: Support for task relations in SyncML
  Queue              | Nag
  Version            | 2.3.1
  Type               | Enhancement
  State              | Accepted
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2010-03-06 05:03) wrote:

> Hi Jan,
>
>> We can't use the client's UID because many clients don't really
>> create GUIDs
> I'm not sure how you mean this. As far as I understand the server  
> needs to assign and send the UID (not GUID) and the client just uses  
> them.

I'm talking about objects created by the device. Some devices assign  
them UIDs that are simply incrementing integers. These are of course  
not globally unique IDs so we can't rely on them.

>> Thus we don't write or read UID fields during import/export [...]
> Interestingly, when I *export* tasks the UID and RELATED-TO *are*  
> written properly. Only when syncing they are not.

Yes, because they are explicitly removed during synchronization.

> I found this analysis of the problem by the synthesis developers helpful:
> http://forum.synthesis.ch/showpost.php?p=3204&postcount=7
>
> So this seems like a horde bug to me, or am I missing something?

No, it's rather a side-effect of a workaround in Horde for broken  
SyncML clients.