[Cosmo-dev] cosmo 0.5.0 and evolution 2.8

[Stephen Reindl]

Hi all,

My name is Stephen Reindl and I'm currently working (for some more time)
for a small consulting company as a project leader. As I need to
rearrange my calendars to a private platform while leaving the company,
I decided to use "cosmo" 0.5.0 as the server platform. 

First of all: Smart tool... Bundling both, the application server (i.e.
webdav, caldav, ...) and the front-end for web-access into one
application is (from my point of view) smart as this enables immediately
a way to check that everything that's transferred from outside is
visible and correct and I can access my calendars from everywhere.

On windows I use Thunderbird together with lightning 0.3 to access my
remove calendar.

If I'm working on the linux side I use evolution (version 2.8.1) to
access mails and calendars. 

Now the problem: evolution is not compliant to the current "draft" of
the caldav format. It still sends the "is-defined" tag for the content
filter when accessing caldav archives. As this tag is renamed to
"is-not-defined" in recent versions of the RFC, the server throws an
exception. I think that both parties have to be more flexible on how to
pass this information. evolution should allow to specify the version
(i.e. draft) to be used (and therefore send either "is-defined" or
"is-not-defined") and cosmo should ignore "is-defined" for some time (at
least print a warning).

The attached patch at least enables evolution to access caldav archives
(and cosmo is printing a warning message into the log file).

Maybe this patch finds your interest.

With Best Regards

Stephen Reindl

-- 
Stephen Reindl <sreindl at sreindl.de>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: diff
Type: text/x-patch
Size: 2561 bytes
Desc: not available
Url : http://lists.osafoundation.org/pipermail/cosmo-dev/attachments/20061107/e1f87c24/diff.bin