I made a similar javascript library, for identical purposes, few months ago
(not as advanced though :). What i realized is that acting this way was not a
good idea, because i was losing some views benefits ; especially the facts that
you always get a small chunk of the results ; you collapse a thread, you expand
another, etc. Thus, users were not downloading a huge html page, but lots of
small html pages. When you have thousands of entries, i'm sure that's much more
convenient (would your users accept to download ~x00Kb pages and wait for the
tree to compute ?). And browsing on several pages does not help us in that
issue.
I made a similar javascript library, for identical purposes, few months ago (not as advanced though :). What i realized is that acting this way was not a good idea, because i was losing some views benefits ; especially the facts that you always get a small chunk of the results ; you collapse a thread, you expand another, etc. Thus, users were not downloading a huge html page, but lots of small html pages. When you have thousands of entries, i'm sure that's much more convenient (would your users accept to download ~x00Kb pages and wait for the tree to compute ?). And browsing on several pages does not help us in that issue.