[Ietf-caldav] Dead properties on CalDAV events / folders

[Julian Reschke]

Mike Shaver wrote:
> On 12/19/05, Kervin L. Pierre <kervin at adevsoft.com> wrote:
>> Or the client could assume that what it
>> sent is not necessarily what the server
>> will store, and that the ETag pertains
>> to what was stored?  Why won't that
>> option work?
> 
> What good does that do the client?  It can't use that ETag in the
> future to know if it needs an update, because it don't know what data
> is signified by that ETag, right?

You know that it's the data you have PUT, except for whatver the server 
felt rewriting. How does it matter, unless you want to do a subsequent 
GET with Range header?

Best regards, Julian