Re: gallery ordering issue

> For reference, how nested is your gallery structure (i.e., what is the
> deepest level)?

I think I went 2 or 3 deep just for testing.  I haven't really utilized the
nested galleries much otherwise. All but about 3 galleries are converted from
my old photo album, which didn't allow subgalleries.

>  From my initial look at the DataTree driver code, it seems that it
> wasn't really optimized for deeply nested trees...  I say this because
> in order to call the getObjectById() function, you have to call
> getName() which in turn loads the entire tree up from the requested
> object to the root... (the odd thing is, this is done so that you can
> call another function, getId() to convert the name back into an id...
> though I'm not sure if it's the same id or not in order to do the actual
> lookup of the requested object).

This sounds pretty much like what I was seeing during development (loading way
more than necessary for a gallery list).  But, it's been a while, so I don't
remember specifics.

--Ben
-- 
ansel mailing list - Join the hunt: http://horde.org/bounties/#ansel
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [email protected]