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

* Your Email Address
* Spam protection	Enter the letters below: __ __ __ __ _______ \ \ / /\ /\ \| \/ \|__ __\| \ \ /\ / / \ / \ \| \ / \| \| \| \ \/ \/ / /\ \ / /\ \ \| \|\/\| \| \| \| \ /\ / ____ \ / ____ \\| \| \| \| \| \| \/ \/_/ \_\_/ \_\_\| \|_\| \|_\|
Comment	>> 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.
Attachment
Watch this ticket