[Tickets #3032] WebDAV / iCal plugin voor kronolith

bugs@bugs.horde.org bugs at bugs.horde.org
Mon Nov 28 08:39:44 PST 2005


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

Ticket URL: http://bugs.horde.org/ticket/?id=3032
-----------------------------------------------------------------------
 Ticket             | 3032
 Updated By         | Jan Schneider <jan at horde.org>
 Summary            | WebDAV / iCal plugin voor kronolith
 Queue              | Kronolith
 Version            | HEAD
 State              | Feedback
 Priority           | 1. Low
 Type               | Enhancement
 Owners             | 
-----------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2005-11-28 08:39) wrote:

> The PUT function calles the import function in the api so the 
> calendar data is imported. I've chosen not to directly call the 
> input, mainly because it could work for kronolith, but I can imagine 
> that other applications cannot work with the import directly. This is 
> mainly because the totally different concepts that are used in the 
> import and put. PUT is based on a path with some file content, which 
> is radically different from importing a certain element in a 
> application. For this reason, I think the usage of an extra function 
> is legitimate.

Makes sense.

> Although I use the import function directly now, I think it would be 
> nicer to use a seperate function for importing a iCalendar file in 
> total. This is because a PUT with a iCalendar file currently results 
> in the entire calendar being deleted and afterwards the elements from 
> the file are added again. This is because otherwise no elements can 
> be deleted (import only allows for adding). Another disadvantage is 
> that every entry is therefore seen as being modified on a PUT. A 
> better solution would be a seperate function that check for each 
> element if it has changed / added / deleted and modifies these 
> entries accordingly.

I think we can live with this disadvantage. GroupDAV and CalDAV probably
deal with that situation anyway.

I added a PDF to http://wiki.horde.org/Doc/Dev/DAV with slides from a
meeting with the GroupDAV guys on this year's LinuxTag, in case you're
interested.




More information about the bugs mailing list