[OGo-Evolution] OGo - evolution connector uploaded in CVS

[Helge Hess]

On Aug 17, 2006, at 14:54, Shreyas Srinivasan wrote:
> Agree, we can have some way to discover features in OGo before using
> them, so the minimal subset would be Groupdav compatible but people
> can add custom server features to the backend. Right now that could
> be messy, let me figure out an elegant way of doing it.

Would be nice, but possibly overkill. Don't know.

>> Of course an OGo specific connector can integrate better with OGo
>> which is also nice ;-)
>
> Heh, true. I think its important to understand how many servers are
> Groupdav compatible and the kind of server specific features which
> they offer.

Oh, quite a few. In fact even a plain Apache WebDAV server should be  
a valid GroupDAV server! (though not a very clever one :-)

> I mean if we could integrate some useful features which
> are missing in the current Groupdav spec but have most servers
> implementing them , then that would rock big time. No idea how
> feasible that is though.

It isn't very feasable. GroupDAV is a minimal spec which just covers  
iCalendar and vCard items and is fully WebDAV compatible. I would  
like to keep it that way.
In fact iCalendar and vCard itself already have significant  
interoperability issues. (in fact OGo doesn't implement everything in  
iCal)

>> > Because we are only testing against opengroupware we wont find any
>> > issues concerning other server implementations.
> True, but i would like it to work with most GROUPDAV servers, just  
> helps
> adoption as Helge stated.

Yeah, would be cool. But having additional OGo features in Evo would  
be very cool too! :-)

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