Re: [Evolution-hackers] Evolution calendar backend

> From: Adam Tauno Williams <awilliam opengroupware us>
> To: evolution-hackers gnome org
> Subject: Re: [Evolution-hackers] Evolution calendar backend
> Date: Sat, 22 Jan 2011 14:59:31 -0500 (01/22/2011 01:59:31 PM)
> RFC4891

> 4.1.  Calendar Object Resources


>            The UID property value of the calendar components contained
in a
>            calendar object resource MUST be unique in the scope of the
>            collection in which they are stored.
>            Calendar components in a calendar collection that have
different UID
>            property values MUST be stored in separate calendar object
>            Calendar components with the same UID property value, in a
>            calendar collection, MUST be contained in the same calendar
>            resource.  


>            The VEVENT component with the UID value "1 example com"
would be
>            stored in its own calendar object resource.  The two VEVENT
>            components with the UID value "2 example com", which
represent a
>            recurring event where one recurrence instance has been
>            would be stored in the same calendar object resource.

I take it from the above reply that the code handling items with the
same UID are for handling recurrences.  I'll look closer at the caldav
spec and see if the sync code makes more sense.

Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]