On Oct 29, 2010, at 2:05 PM, ChadDavis <[email protected]> wrote:
> On Fri, Oct 29, 2010 at 12:57 PM, Rakesh Vidyadharan <[email protected]> wrote: >> >> On 28 Oct 2010, at 16:12, ChadDavis wrote: >> >>> I'm working on a CMS based on Jackrabbit. The UI is a RIA, of sorts. >>> The user is presented with a file tree structure. If they are at the >>> root folder, then the tree is pretty big. I *need* to have the whole >>> data model in order to build the file tree in the UI, but it's an >>> obviously costly act. I'm now trying to determine my options for >>> making this process more efficient. Here's a couple I've thought of, >>> and I'm hoping that someone will provide some guidance. >>> >>> 1) I could load only a portion of the tree, then use Ajax techniques >>> to lazy load the deeper folders in the tree as the user works through >>> them >> >> I use this technique and have not had any issues. >> > > How much of the data model do you pull down on the first request? Do > you wait for the user to click on a folder to get more? I have a configured page size that I use with the node iterator for paginating potentially large nodes. Yes, I wait for user interaction to pull in data for a selected node. The tree model is initially populated with just the top level nodes. Rakesh
