The dasl basic search specification specifies that the select clause can either contain a single <d:prop><property-to-select></d:prop> element or else <d:allprop/> . In order for a basic search request to mimic a propfind this lacks the ability to select multiple properties of choice. What I would like to be able to do is this:
<d:select> <d:prop><d:displayname/></d:prop> <d:prop><H:newsdate/></d:prop> <d:prop><Z:authors/></d:prop> </d:select>
Notice that this does not conflict with the spec but rather expands on it. This would allow one to optimize performance by doing a search instead of a propfind. With the new sql dasl implementation (once it stabilizes), depending on what properties you are requesting and what store topology you have configured, this would mean only 1 (one, uno, un, ein, een) SQL query gets executed instead of Oxn (x being the number of properties, n being the number of resources in the propfind result)
WDYAT?
-- Unico
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
