- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 13 Jul 2009 22:12:22 +0200
- To: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
- CC: caldav@ietf.org, calsify@ietf.org, w3c-dist-auth@w3.org, Cyrus Daboo <cyrus@daboo.name>, Alexey Melnikov <alexey.melnikov@isode.com>, Lisa Dusseault <Lisa.Dusseault@messagingarchitects.com>
Julian Reschke wrote: > ... > 8. Conditional Requests on Scheduling Object Resources > > In order to do that, this specification introduces a new WebDAV > resource property CALDAV:schedule-tag with a corresponding response > header "Schedule-Tag", and a new "If-Schedule-Tag-Match" request > header to allow client changes to be appropriately merged with server > changes in the case where the changes on the server were the result > of an "inconsequential" scheduling message update. An > "inconsequential" scheduling message is one which simply updates the > status information of Attendees due to a reply from an Attendee. > > JR: that sounds really heavy-weight; I think it would be good to discuss > this scenario over on the HTTPbis working group's mailing list. Even if new > state tokens need to be added it is not totally clear why the RFC4918 > can not be used for checking. > ... Sorry. I meant to say: "...why the RFC4918 'If' header can not be used...". BR, Julian
Received on Monday, 13 July 2009 20:13:15 UTC