[kronolith] WebDAV backend!

[Johan Ekblad]

Jan Schneider wrote:
> Zitat von Johan Ekblad <jka at eminds.se>:
> 
>> Hi. I'm new to this list and I'm planning to build a WebDAV backend
>> using iCal for Kronolith. My goal is that Kronolith may read and write
>> Calendar entries to a ics-file placed on a WebDAV server (For example
>> apache with only the mod_dav and mod_dav_fs extensions) so that for
>> example Sunbird and Kronolith may use the same Calendar.
>>
>> In the future the code may be used for someone implementing support
>> against a CalDAV server (but right now I'm planning to start with WebDAV)
> 
> Please note that we are working (slowly) on making Kronolith a  
> WebDAV/CalDAV *server*, which makes more sense IMO. But that shouldn't  
> keep you from creating a WebDAV *client* driver for Kronolith.
> 
>> I would like a few questions answered.
>>
>> In the TODO-list there are two points:
>>
>> ------------
>>
>> - Remove the assumption that each calendar is using the same backend.
>> Ideally it should be possible to have a local calendar using sql or
>> kolab and a remote calendar using another driver (eg wcap or whatever
>> mozilla uses).
>>
>> Is it OK to assume the same backend (WedDAV/iCAL) for all calendars in
>> my implementation?
> 
> Yes, because that's what we still do in all the other drivers.
> 
>> - Allow publishing calendars to a remote site as iCalendar files.
>>
>> This is a different, since it only exports a Calendar to a WebDAV
>> server, but I guess some of my code may be used to implement this.
> 
> Correct.
> 
>> As I understand it, all the Kolab backend-operations end up in
>> IMAP-calls against the Kolab server, so no calendar info is kept in a
>> local Kronolith database.
> 
> True.
> 
>> Maybe a more simple approach is to cache the calendar in a local SQL
>> database and only read/write to the WebDAV server when you write/refresh
>> this calender. This is easier to implement and maybe faster than
>> accessing a remote WebDAV server each time. What do you think?
> 
> That makes sense, but it should be optional. If you are going to do  
> that, you should extend Kronolith_Driver_sql with your new driver.
> 

Thanks for the input, that seems to be a good place to start.

I'm planning to use the Pear library HTTP_WebDAV_Client. It's currently 
in beta (0.9.7), but I'll give it a try, hope it's OK

   //regards: Johan Ekblad