Tickets :: Comment on [#3032] WebDAV / iCal support for Kronolith

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

Saved Queries