- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 12 Aug 2002 10:00:43 +0200
- To: "Wallmer, Martin" <Martin.Wallmer@softwareag.com>, <www-webdav-dasl@w3.org>, <ietf-dav-versioning@w3.org>
- Cc: "Kazeroni, Ladan" <Ladan.Kazeroni@softwareag.com>, "Nevermann, Dr., Peter" <Peter.Nevermann@softwareag.com>, "Pill, Juergen" <Juergen.Pill@softwareag.com>
I think we should make SEARCH compatible to RFC3253/ACL -- that is DAV:allprop behaves just like for PROPFIND. > -----Original Message----- > From: www-webdav-dasl-request@w3.org > [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Wallmer, Martin > Sent: Monday, August 12, 2002 9:38 AM > To: 'www-webdav-dasl@w3.org'; 'ietf-dav-versioning@w3.org' > Cc: Kazeroni, Ladan; Nevermann, Dr., Peter; Pill, Juergen > Subject: DASL and DELTA-V properties > > > > Hi, > > should a DAV:allprop SEARCH on a Delta-V enabled resource return > all Delta-V > properties as well? According to > > --- > RFC 3253 > > 3.11 Additional PROPFIND Semantics > > A DAV:allprop PROPFIND request SHOULD NOT return any of the > properties defined by this document. This allows a versioning server > to perform efficiently when a naive client, which does not understand > the cost of asking a server to compute all possible live properties, > issues a DAV:allprop PROPFIND request. > --- > > PROPFIND should not return them. Is this true for SEARCH as well? > Is there a > need to define the behaviour for SEARCH as well? > > Regards, > > Martin Wallmer > Research & Development > Software AG ++49 6151 92 1831 > Uhlandstr. 12 > D 64297 Darmstadt > >
Received on Monday, 12 August 2002 04:01:22 UTC