[OGo-Evolution] working mangling daemon allowing basic OGo-Evolution

[Erik Romijn]

On Tue, 2004-10-19 at 15:40 +0200, Helge Hess wrote:
> Thanks to Erik's work I was able to fix ZideStore to provide at least 
> minimal Evo Connector 2.0.2 connectivity. That is, you can now properly 
> login at ZideStore and even see some data.

Is this ZideStore version also already available in trunk?

I have just tested with the ex2ogo daemon and the latest trunk packages
for suse that were available yesterday (r256.7).
Testing with Evolution and Connector 2.0.1 basic writing support for
calendar items seems to work.
Without having looked into it any further, recurrency and alarms are not
working.
I have looked into read support for recurrency for evo<->ogo and I
noticed that OGo sets both a few properties in the item and ZideStore
returns another appointment item for each occurrence of the appointment.
With ex2ogo for reading recurrency is not handled, ZideStore just tells
it every occurrence of the item.
Does the client really have to insert all the different occurrences of
the item or does ZideStore just generate this when requested? In the
latter case it should be not too hard to let Evo and ZideStore
understand each others data related to recurrency.

Task and Contact writing will be a bit harder, as the connector uses the
PROPPATCH request which is not implemented by ZideStore. I haven't
looked into what exactly the request contains. In ex2ogo this should
probably be handled by mangling it into a PUT if possible until
ZideStore understands the PROPPATCH.

Greetings,
Erik Romijn