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

[Helge Hess]

On Oct 21, 2004, at 12:22, Erik Romijn wrote:
>> ZideStore currently returns 501 whenever it encounters a requests 
>> which
>> it basically understands but can't handle. If there is a better
>> response code for this case, let me know.
> Maybe a 405 would be appropriate.

I think its pretty much the same like 501.

> Changing it to a 201 works. Evo now also displays the item after it has
> been added, without evo thinking it was successful a restart was
> required to display it.
...
> Shouldn't be too hard to implement in ZideStore I guess.

Should be in trunk r272.

> On the required restart of evo: as far as I understood from the
> connector people the connector uses SUBSCRIBE to make the server tell
> the connector when data is updated. In it's current form it doesn't 
> seem
> to work, haven't looked into it very far.

Well, SOPE supports SUBSCRIBE and maintains a subscription list 
(sope-appserver/NGObjWeb/WebDAV/SoSubscriptionManager.[hm]). But 
ZideStore never sends notifications.

I'm not yet sure what is the best time to send which subscriptions. I 
suppose ZideStore should send refresh notifications every n-minutes 
(because it can't know whether other services changed something in the 
store).

In addition the current subscription manager keeps subscriptions in RAM 
and therefore doesn't work with multiple ZideStore instances.

In short: a proper/complete implementation of subscribe is a _lot_ of 
work. I don't think its worth the effort. Rather post notifications at 
"clever" times ;-)

> I think I'll start taking a look at compatibility between Evo's alarm
> and OGo's reminder. It guess it should be possible to convert between
> the two.

OK, great. I think for Outlook we just store the alarm in a separate 
database field.

Greets,
   Helge
-- 
http://docs.opengroupware.org/Members/helge/
OpenGroupware.org