Re: [caldav] [VCARDDAV] new webdav sync draft

Julian Reschke <julian.reschke@gmx.de> Mon, 07 December 2009 21:58 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: caldav@core3.amsl.com
Delivered-To: caldav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1CF503A69A2 for <caldav@core3.amsl.com>; Mon, 7 Dec 2009 13:58:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.224
X-Spam-Level:
X-Spam-Status: No, score=-4.224 tagged_above=-999 required=5 tests=[AWL=-1.625, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jxtf8vp7FjyD for <caldav@core3.amsl.com>; Mon, 7 Dec 2009 13:58:05 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 7614A3A694E for <caldav@ietf.org>; Mon, 7 Dec 2009 13:58:04 -0800 (PST)
Received: (qmail invoked by alias); 07 Dec 2009 21:57:49 -0000
Received: from p508FF787.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.247.135] by mail.gmx.net (mp064) with SMTP; 07 Dec 2009 22:57:49 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18gpD18oPcgqHR81BlgCHzQKAt8i1ej3ELzGlRxO5 IjwLz7QY4GcdFR
Message-ID: <4B1D7A59.2090902@gmx.de>
Date: Mon, 07 Dec 2009 22:57:45 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Helge Hess <helge.hess@opengroupware.org>
References: <4B057E6B.7040808@sun.com> <FC4CE9C0-0F2C-4F4A-8F22-DAE3F1AA6B4D@opengroupware.org> <A965C432C02C1101E4F0487F@caldav.corp.apple.com> <15817EA7-94F1-4EDF-AF0C-744F4C319AEC@opengroupware.org>
In-Reply-To: <15817EA7-94F1-4EDF-AF0C-744F4C319AEC@opengroupware.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.6
Cc: Arnaud Quillaud <Arnaud.Quillaud@Sun.COM>, caldav@ietf.org, w3c-dist-auth@w3.org, vcarddav@ietf.org
Subject: Re: [caldav] [VCARDDAV] new webdav sync draft
X-BeenThere: caldav@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <caldav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/caldav>
List-Post: <mailto:caldav@ietf.org>
List-Help: <mailto:caldav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Dec 2009 21:58:05 -0000

Helge Hess wrote:
> On 07.12.2009, at 16:55, Cyrus Daboo wrote:
>> Just to clarify - right now the spec says that a resource that is deleted and re-created is reported as "new" if a sync-token prior to the deletion is given in the REPORT.
> 
> Ah, OK. I would have expected a "deleted" and a "new" entry in such a case.
> 
> Now thinking about it, I think it might be an issue if a resource in the cache is replaced with an entirely new resource.
> Eg the client might have (real world: is likely to have) extra client-side data which is only valid for the 'old' resource.
> 
> But then, the client can't discover that specific situation with the regular PROPFIND either. And it won't be terribly common, as new URLs usually change in most systems.

It could if the server supports DAV:resourceid. (see 
draft-ietf-webdav-bind).

> ...

BR, Julian