- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Sat, 21 Nov 2009 07:56:35 +0100
- To: Andrew McMillan <andrew@morphoss.com>
- CC: Arnaud Quillaud <Arnaud.Quillaud@Sun.COM>, w3c-dist-auth@w3.org
Andrew McMillan wrote: > On Fri, 2009-11-20 at 17:13 +0100, Arnaud Quillaud wrote: >> On 11/19/09 11:01 PM, Andrew McMillan wrote: >>> In particular when synchronising a calendar collection it would be >>> desirable for the report to be able to return 'caldav:calendar-data', >>> which in many cases would then save the further round-trip of a >>> calendar-multiget report following this report. I assume there would be >>> similar advantages in retrieving the actual changed data in other extensions. > > >> A client may ask for any property... as long as it is defined as >> such... calendar-data is not one of them. See >> http://tools.ietf.org/html/rfc4791#section-9.6 : >> << >> However, the CALDAV:calendar-data XML element is >> not a WebDAV property and, as such, is not returned in PROPFIND >> responses > > Ah, what a shame. Can I take it from this that CardDAV will also suffer > from this limitation? > ... Can't resist: "I told you so". Pseudo-properties are bad; they require more special cases, create ambiguities and confusion. > .. BR, Julian
Received on Saturday, 21 November 2009 07:24:20 UTC