Re: enhancements/fixes for slide 2.1

Hi Max and Slide list...

I was wondering if your fixes to the DASL ordering and limiting have  
been added to Slide yet?
I'm working with a 6 months old Slide build or so and ordering seems  
to be broken although limiting works.

Ordering by getlastmodified e.g. in this DASL search does not order  
the results:

<D:searchrequest xmlns:D='DAV:' xmlns:S='http://jakarta.apache.org/ 
slide/'>
<D:basicsearch>
<D:select><D:prop><D:getcontentlength/><D:creationdate/ 
 ><D:displayname/><D:getlastmodified/></D:prop></D:select>
<D:from><D:scope><D:href>files</D:href><D:depth>infinity</D:depth></ 
D:scope></D:from>
<D:where>
<D:and>
<D:or>
<D:contains>***</D:contains>
<S:property-contains><D:prop><D:displayname/></D:prop><D:literal>***</ 
D:literal>
</S:property-contains><S:property-contains>
<D:prop><D:creator-displayname/></D:prop><D:literal>***</D:literal>
</S:property-contains>
<S:property-contains><D:prop><D:comment/></D:prop><D:literal>***</ 
D:literal></S:property-contains>
</D:or>
<D:not-is-collection/>
</D:and>
</D:where>
<D:orderby><D:order><D:prop><D:getlastmodified/></ 
D:prop><D:descending/></D:order></D:orderby>
</D:basicsearch></D:searchrequest>



On 20.2.2006, at 11:09, Max Pfingsthorn wrote:

> Dear all,
>
> I hate to reply to myself, but I was just wondering if the offer  
> still stands... I would love to help out and it would be great if  
> you guys gave me that chance!
>
> Best,
> Max
>
>> -----Original Message-----
>> From: Max Pfingsthorn
>> Sent: Tuesday, February 14, 2006 11:20
>> To: Slide Developers Mailing List
>> Subject: RE: enhancements/fixes for slide 2.1
>>
>>
>> Hello everyone!
>>
>>> -----Original Message-----
>>> From: [email protected] [mailto:[email protected]]
>>> Sent: Saturday, February 11, 2006 12:33
>>> To: 'Slide Developers Mailing List'
>>> Subject: AW: enhancements/fixes for slide 2.1
>>>
>>> Hi Hippo!
>>
>> Hippo is just my employer ;) Just call me Max.
>>
>>> Fromm y point of view it would be great if you would become a slide
>>> committer and could add patches to the sources directly. If you are
>>> interested, I would start a voting thread on this mailing list.
>>
>> That would be great! I would be very honored.
>>
>>> I think most of your patches are very helpful for the slide
>> community.
>>
>> Thanks, I do my best.
>>
>>> One comment to your patches regarding the lucene-based search:
>>> If you use lucene directly to limit the results this might
>> cause some
>>> trouble if you are using acl's. The acl's get evaluated after slide
>>> retrieves the search result from lucene. If you for example
>>> specify a limit
>>> of 10 results and the user executing the DASL-request has no
>>> permissions to
>>> read half of them, he would only get 5 files even if he
>>> specified to get 10.
>>> So it would be very helpful to have a configurable switch to
>>> select if you
>>> want to have a fast system (with the risk of wrong number of
>>> results) or a
>>> slower search with correct results.
>>
>> Actually, you cannot tell Lucene to only return so many hits.
>> The nice thing about Lucene's Hits datastructure is that it
>> lazy-loads data from the index. That way, it can return the
>> full structure, without much of the overhead, and you can
>> decide how many you access yourself. What I do is to iterate
>> through the Hits until I generated as many authorized results
>> as needed. What makes it fast is that sorting is done in
>> Lucene as well, so even then, you don't have to load all
>> results in memory and sort them there as it's done right now.
>>
>>> Why have you used JMS to notify cocoon? Have you had a look at the
>>> Notification abilities in the slide webdavlib?
>>
>> I wasn't aware that the webdavlib had such a feature. Also,
>> when I joined the team here, JMS notification was already  
>> implemented.
>>
>> Bye!
>> max
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>