Morris Jobke aab646a9d0 Update system addressbook card only when there was a change based on a cached etag ... Due to our old and new hook system the card dav backend listens to old and new hooks. This triggers this code multiple times and always causes an update. With this change we cache the etag during a request and only trigger the update if the etag has changed. This does not catches all not needed updates, but it does not need another round trip to the database and still covers most cases where multiple attributes are updated during one single request. Signed-off-by: Morris Jobke <hey@morrisjobke.de>		2020-07-09 11:43:58 +02:00
..
misc	Addressbook sharing added based on a simplified approach which is based on calendar sharing standard	2015-11-19 11:34:31 +01:00
travis	fix caldav tests	2018-11-15 12:35:05 +01:00
unit	Update system addressbook card only when there was a change based on a cached etag	2020-07-09 11:43:58 +02:00