[Ietf-caldav] Fwd: Summary of ETag related issues in RFC2518bis
Kervin L. Pierre
kervin at adevsoft.com
Thu Dec 22 07:32:46 PST 2005
Helge Hess wrote:
> 2-a) GET /blah.ics, if-match: etag=ABC
But could that GET be inconclusive since the server
may have split the ICS file into multiple resources?
Ie. you get blah.ics back on your "2-a" GET, it has
the ETag from the 205 PUT but it does not represent
the ICal that was originally sent since the server
created blah1.ics, blah2.ics, etc. in response to
the original ICal.
> BTW: I think the issue of conflicts is very much underestimated.
I agree, which is why I am leaning on having the
client require WebDAV Class 2 on logon, and use
More information about the Ietf-caldav