RE: DASL and DELTA-V properties
"Clemm, Geoff" <[email protected]>
| Newsgroups | gmane.ietf.deltav |
|---|---|
| Message-ID | <3906C56A7BD1F54593344C05BD1374B107D7B81A@SUS-MA1IT01> |
I agree with Julian. DAV:allprop SEARCH should be defined to have the same behavior as DAV:allprop. In particular, it should not search RFC-3253 properties. The current proposal for the next revision of 2518 is that it should only search dead properties and properties defined in RFC-2518. Cheers, Geoff -----Original Message----- From: Julian Reschke [mailto:[email protected]] Sent: Monday, August 12, 2002 4:01 AM To: Wallmer, Martin; [email protected]; [email protected] Cc: Kazeroni, Ladan; Nevermann, Dr., Peter; Pill, Juergen Subject: RE: DASL and DELTA-V properties I think we should make SEARCH compatible to RFC3253/ACL -- that is DAV:allprop behaves just like for PROPFIND. > -----Original Message----- > From: [email protected] > [mailto:[email protected]]On Behalf Of Wallmer, Martin > Sent: Monday, August 12, 2002 9:38 AM > To: '[email protected]'; '[email protected]' > 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 > >