Lennon Day-Reynolds wrote:

> In your "home LAN" example, you really do only need one WebDAV server.
> Each client (aka copy of Sunbird) then publishes a copy of its
> calendar data to that server. When they exchange data, it's through
> the server, not directly from client to client.

There's no assurance that any given machine will be running.  I'd prefer 
if I could just point to the machine (or URL) that has the data I want, 
and pull it back.  I also want to yank calendar info from applications 
that are not aware they are providing ical data.

For example, I use a wiki as a PIM.  It has names, addresss, birth 
dates, project plans, and who knows what else.

If I add a wiki page to hold personal data about a friend, and that page 
has a birthday date in it, I would like some process to magically 
recognize that and add publish it as calendar data.

(Another way might be to write a wiki plugin such that a request to a 
special wiki URL returns an ical response.  Hmm ... )

> 
> Looking at the Sunbird docs, it also appears that you can use FTP to
> publish and subscribe to calendars. You'd lose iCal compatibility, but
> it could be an effective stopgap until someone has a pure Ruby WebDAV
> server ready to go.


I did a simple experiment, and it appears that when Sunbird fetches a 
remote calendar it does a simple GET.  I was able to have WEBrick spit 
back a text file with calendar data, and Sunbird added the events to my 
calendar.

When I asked Sunbird to publish its calendar to WEBrick, it did a PUT. 
I have to go examine the headers to see just what it was trying to send.

It may be that true WebDAV is not needed for Sunbird-specific  interaction.


James