[GroupDAV] Evolution Connector; Calendar Selection

[Adam Tauno Williams]

>> Against my person server (much less data) it seems to work fine.  But
>> I'm skeptical about using GroupDAV with a server containing >10,000
>> contacts anyway - that is allot of GETs. :)
> Never fear: the same bunch of degenerates who brought us the insanely
> over-engineered and over-complex CalDAV protocol are now talking about
> something called "CardDAV" which will supposedly solve that problem in the
> same broken, over-complicated, difficult-to-implement way that CalDAV
> supposedly solves it for calendars.

Thats OK, if the rate of implementation/adoption is the same as CalDAV =20
I'm be ash in an urn by the time I see a working client/server =20
solution. :)

> (Here's a hint for protocol designers: if you use the REPORT command at
> all, you've gone way overboard in the design and are inviting buggy and
> incomplete implementations.)

 From the CardDAV spec:
"A CardDAV server is a vCard-aware engine combined with a WebDAV
repository.  A WebDAV repository is a set of WebDAV collections,
containing other WebDAV resources, within a unified URL namespace."

It seems like the relation between CardDAV & GroupDAV is the same as =20
between CalDAV & GroupDAV.  A CardDAV server would be a defacto =20
GroupDAV server.