Dick Davies wrote:

> * James Britt <jamesUNDERBARb / neurogami.com> [0810 18:10]:
> 
>>I recently downloaded Sunbird [0], the calendar application from the 
>>Mozilla team. It looks OK, seems to do what I want, even at version 0.2.
>>
>>It has a facility for sharing or exchanging calendar data.  This 
>>requires WebDAV [1], though.  I'd rather not have to run Apache with 
>>mod_webdav on every machine where I want to share a calendar.  I'd 
>>prefer to run a lighter Ruby process that handles the WebDAV requests.
> 
> 
> Surely you just want one webdav server to host the calendar?

Here's a use case: I have three PCs in my house.  I'd like to run 
Sunbird on all of them. When I use Sunbird on my laptop, I want it to be 
able to go exchange calendar data with the other 2 machines.  Sunbird 
speaks WebDAV, so something on the remote boxes must speak WebDAV, too. 
  (Actually, the may be other ways to do this by reading/writing Sunbird 
calendars using another process, but using the built-in Sunbird stuff 
seems simpler to start with.)

When search a server gets a request, I want it to serve up the calendars 
info, but also have it go check other files/processes on the same 
machine (such as wikis and blogs) to see if there is anything that 
should be sent over as calendar data.

So I need a server process of some sort on each machine where I want to 
serve up or accept calendar data.

Another scenario:  A conference is listed on ruby-doc.org.  I want 
people to be able to point Sunbird at some ruby-doc.org URL and have it 
fetch calendar events, so that the conference appears in their 
calendars.  But, I don't want to have to store an iCal file up on 
ruby-doc.org.  Just the blog/web site.  The calendar-server code needs 
to know how to accept WebDAV requests go grab calendar data from the 
blog entries.  Sort of a virtual iCal file proxy.

>  
> 
>>A bigger reason for wanting to have a custom Ruby process handle the 
>>calender sharing is that I want to be able to hook Sunbird into my wikis 
>>and blogs.  It would be sweet if could add a page to a wiki, use some 
>>special markup to indicate that something has a deadline or an 
>>associated calendar date, and have that info appear in all my calendars. 
>> and vice versa.
> 
> 
> That would be excellent. I think a ruby webdav *client* would be more useful
> than a server for a lot of reasons: 
> 
> * DAV is still a moving target
> * all DAV clients suck

I could be handy to have blogs, wikis, etc. speak WebDAV so that they 
could interact with shared calendars.  I believe there is some WebDAV 
client code listed on the RAA.

James