[Registry-dev] getLogs ordering

[Paul Fremantle]

Chathura

Its more useful if you can come up with names that mean something. 
Descending to me doesn't let me know which is first! If you call the 
param recentFirst then there is no mistaking the meaning.

Paul

Chathura C. Ekanayake wrote:
> 
> Hi Jonathan,
> 
> Added "descending" parameter to the Registry.getLogs(...) method. When 
> it's set to true, activities are returned in descending order of the time.
> If it is false, activities are returned in ascending order.
> 
> Thanks,
> Chathura
> 
> Jonathan Marsh wrote:
>>
>> Currently getLogs returns logs in chronological order, which makes 
>> perfect sense when enumerating the history.
>>
>> However, I’m also using it for “recent” activity queries, in which I 
>> want reverse chronological order. Since histories will get long, and 
>> probably need paging (currently I have a 5-item pseudo-paging system), 
>> it’s impractical to read the whole list to get the few most recent items.
>>
>> So would it be poosible to add an “order” parameter to determine 
>> whether the log entries are returned in newest-first or oldest-first 
>> order?
>>
>> *Jonathan Marsh* - http://www.wso2.com - 
>> http://auburnmarshes.spaces.live.com
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Registry-dev mailing list
>> Registry-dev at wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
>>   
> 
> 
> _______________________________________________
> Registry-dev mailing list
> Registry-dev at wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
> 

-- 
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

Office: +1 646 290 8050
Cell: +44 798 447 4618

blog: http://pzf.fremantle.org
paul at wso2.com

"Oxygenating the Web Service Platform", www.wso2.com