Actually the "V" in WebDAV (and CalDAV and CardDAV) is for "versioning". In a perfect world every server would implement RFC 3253 which adds versioning to the base protocol. That would allow you to check out every state your address book had in the past.

Am 27.08.2015 um 00:02 schrieb GJ:
Hi Jan,
too me - the del is too fast and unreversible... ;)

Am 26.08.2015 um 23:48 schrieb Ján Máté:
Hi Gil,

And as always - a "copy and paste" feature out of an read only address book would also be very cool if you want to serve a "master" copy of a adr book to a group of people from witch they can fill their own books...
Multiple copies of one contact creates more problems than it solves. What if the contact is changed? Will you update it in all addressbooks? The good solution here is to share the contact using shared addressbooks, and set proper permissions for these addressbooks. This doesn't mean that I say no for copy functionality, but there are lot of other (much more important) things I want to add/change.

The problem is, that i always have to share a whole adr. book - there is no way to "group" the rights of every single entry. I mean in a perfect world there would be some kind of master adr. book sharing its entrys (with all the changes to it) to sub adr. books - even with mayby - botoom up inheritances.
And in this perfect world there would also be a undelete function and of course - a kind of a "timeline" whats was changes in the entry during the time... ;)

But i know - we´re not living there!





Marten Gajda
Schandauer Straße 34
01309 Dresden

tel: +49 177 4427167

VAT Reg. No.: DE269072391