[Cosmo-dev] New user, perplexed: CalDAV interface with Cosmo

[Brian Moseley]

On 5/27/06, Mikeal Rogers <mikeal at osafoundation.org> wrote:

> We've been working with some of the evolution developers on interop
> issues between evolution and cosmo. I can't remember the status of
> this, Brian will have to comment on it when he gets back. Evolution
> added CalDAV support recently so they may not be supporting the
> entire spec just yet.

we haven't worked with any evolution developers that i know of. bear
was nice enough to write up some instructions for getting evolution to
subscribe to a cosmo calendar. you can find them here:

<http://wiki.osafoundation.org/bin/view/Documentation/CosmoWithEvolution>

evolution does not support creating caldav calendars on any server. in
fact, the only two clients i know that do have this support are
chandler and scooby.

> > * Setting the URL in Evolution as caldav://FQDN:port/cosmo/home/shared
> > doesn't allow me to enter/view anything (but then there's nothing
> > to view
> > yet).  Specifying a filename at the end of that URL doesn't seem to
> > help.
> > What I seem to get in the access.log are 401, 409 and 411 errors.

that's because /home/shared/ is your home directory. it is not a
calendar itself. you have to cause a calendar to be created in your
homedir. as i mentioned above, you could do this either by:

1) logging into scooby (this will autocreate a calendar named "Scooby") or
2) using chandler to share its calendar (this will copy the chandler
calendar to cosmo)

> This may be somewhere that we either haven't finished Evolution
> interop, or Evolution doesn't fully support MKCALENDAR yet.

it does not.

> There are two bundles, one with Scooby0.1-release and one with
> Scooby0.2-trunk, although we are very proud of scooby 0.2, it's very
> pretty :), it isn't released yet and hasn't gone through a QA cycle.

and it just might have a bug that is preventing you from logging in
for some reason.

> In 0.3 we added a nifty little feature. Since CalDAV doesn't specify
> a behavior when doing a GET request on a calendar resource we
> implemented a webcal response when doing this.
>
> If you want a read only webcal that you can view in iCal (and I think
> Evolution although I haven't tried it) you could use this feature.

that's actually been in cosmo since 0.2.