On Wed, 2006-05-24 at 09:21 -0400, Don Levey wrote: > On Wed, 2006-05-24 at 09:23 +0200, Christian Borup wrote: > > On Tue, 2006-05-23 at 20:32 -0400, Don Levey wrote: > > > > The eventual goal is for both my wife and I to maintain a central > > > calendar of our appointments and commitments, and for the kids.
I'm using Google calendars for my home/family things, mainly because they are accessible from everywhere and hence my wife can update them from behind her company's draconian firewall. > > > > It sounds like the CalDAV (is this like WebDAV?) would allow me to skip > > > the publishing step and just maintain the central file - is that > > > correct? If so, that would be even easier. OSAF has something called > > > "Chandler"; is that what you're referring to? If so, I can try to > > > install that on my server and access via Evolution. > > > > Actually, Cosmo is the CalDAV server. But it is part of the same > > project. > > Yes, Cosmo is what I use for my work things. > > CalDAV is indeed like WebDAV. It is WebDAV with a number of calendar > > specific extensions. > > OK, so it sounds like (coupled with the above) the CalDAV-based calendar > is a mostly read-only view, users would update their own local calendars > and publish events to the server. Have I got that correctly? May I > assume that I can connect to a CalDAV calendar using the WebDAV option > in Evolution? CalDAV is a R/W solution and updates whenever a change is made - you don't have to 'publish' the calendar. You connect to it using CalDAV in Evo, it's a separate option to WebDAV. Basically as far as I can tell the WebDAV method just dumps a unified ICAL file onto the server that other things can read, CalDAV transfers small ICAL files representing individual events which then get read into the main Cosmo (or whatever) store. P. _______________________________________________ Evolution-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/evolution-list
