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

[Erik Romijn]

On Thu, 2004-10-21 at 12:59 +0200, Helge Hess wrote:
> 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.

Yes, but maybe it would be useful to use different responses for an
unknown request and a known request with unprocessable data.

> 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 ;-)

We could just make ZideStore send a notification at regular intervals.
This would cause evo to refresh it's data; if no new data is available
that won't matter. It would not be very pretty, but at least it would
work ;-)

> > 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.

You mean for ZideLook? I think it would be nice if OGo reminder and Evo
alarm were connected to each other and not in seperated fields.

Greetings,
Erik