[Tickets #3032] WebDAV / iCal plugin voor kronolith

bugs@bugs.horde.org bugs at bugs.horde.org
Thu Nov 24 04:21:34 PST 2005


Ticket URL: http://bugs.horde.org/ticket/?id=3032
 Ticket             | 3032
 Updated By         | d.bussink at student.utwente.nl
 Summary            | WebDAV / iCal plugin voor kronolith
 Queue              | Kronolith
 Version            | HEAD
 State              | Feedback
 Priority           | 1. Low
 Type               | Enhancement
 Owners             | 

d.bussink at student.utwente.nl (2005-11-24 04:21) wrote:

> Great, patches are welcome. The webdav support is still incomplete, so 
> any help to finalize this would be awesome. Please note that whatever you

> change must not break "regular" webdav access through /horde/rpc.php.

I'm wondering whether it would be possible to also model this in the generic
webdav access. Essentialy it is nothing more that a list of file that are
icalendar files. Problem only is that which files will be there should be
dependant on the authentification, don't think it would be really nice to be
able to see other people's calendars, albeit only the file/calendar name. I
also don't know what the policy is here, so whether this is even wanted or
that a seperate interface file is a better solution.

> I'm also curious how you solve the problem that clients provide there own

> "file names" when PUTting data to the webdav server that we can't use 
> internally in Kronolith. But I'll probably find out if I actually look at
your code. ;)

Currenty nothing really happens ;) This patch is really something to get it
to work, I was really getting frustrated with the fact that these solutions
where not really available. I've tried Open-Xchange, but here the calendar
didn't let me delete events over iCal/WebDAV and their webmail interface is
really crap. 

I then saw the ics.php file in the latest cvs and saw how easy it wat, so I
made this thing quickly so I can use it for my personal use and the study
association  where I'm a member of. The main reason I committed it, is
because I saw more people having the same problem, I also noticed similar
requests on the Horde mailing lists.

More information about the bugs mailing list