[dev] ansel (datathree) limit

[Chuck Hagenbuch]

Quoting duck at obala.net:

> As I see Ansel cannot retirves just the separate parts of needed data 
> science is an Share or better an DataThree limitation. We cannot 
> provide the right crierias for selecting just a part of 
> Shares/DataThrees. We can select levels of three not how many chils 
> we wont back. So DataThree::getByAttributes and its calls must be 
> expanded to specify the limit from/to parameters before any work on 
> Ansel can be done. I think that limitation of result would be usefull 
> in many other cases in other aps too.

I'm always open for suggestions (better yet, patches) on ways to improve the
flexibility and performance of the DataTree. Bring it on. :)

-chuck

--
"Regard my poor demoralized mule!" - Juan Valdez