- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 07 Dec 2009 22:57:45 +0100
- To: Helge Hess <helge.hess@opengroupware.org>
- CC: Cyrus Daboo <cyrus@daboo.name>, Arnaud Quillaud <Arnaud.Quillaud@Sun.COM>, caldav@ietf.org, w3c-dist-auth@w3.org, vcarddav@ietf.org
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
Received on Monday, 7 December 2009 21:58:26 UTC