[OGo-Evolution] Started project to join Evo2.2 and OGo 1.0

[Erik Romijn]

On Tue, 2004-11-30 at 13:59 +0100, Alvaro del Castillo wrote:
> > > Erik, it will be great to work with you if possible, but we have hard
> > > time limits in the project.
> > 
> > I would like to - but probably I can only find 8 hours a week for this.
> > Also my (gnome) C/C++ knowledge is not much.
> > If this gets working I can drop ex2ogo and just join on this - although
> > I would have to talk about that to my boss first.
> > 
> > So if you can use someone for only that time a week - I would like to
> > join.
> 
> Great! As soon as we start coding, we will need people that take the
> conenctor, try to compile it and check it against OGo 1.0.

We can run quick beta tests on mostly any time at work days, allowing
quick bug hunting.

I also learned quite some ZideStore WebDAV - could help out with that
too.

If needed and if I can do something useful I can probably get some more
time for this - this connector is important for our company.

> The connector will be GPL, not sure in the OGo library also, or we use a
> LGPL license better.

The newest version, 0.1.2.1, is now available under LGPL on the site. I
didn't relicense the others as they contain nothing useful that isn't in
0.1.2.1.

Another question on your connector: will it also feature caching of
data? With that I mean that if evo requests some calendar items from
zidestore, will it keep that data or it's modification dates in memory
so that if evo refreshes there will not be any unnecesary slow zidestore
requests? One of the old ex2ogo problems is that it doesn't cache and
gets quite slow. although a native connector would already be faster I
think caching would still be good for performance and for the load on
the zidestore server.

greets,
Erik