I think you'd want to look into a "load on demand" approach... Why marshal up all the data for all the nodes when most won't be visible? I'm assuming you show the subsidiary level(s) collapsed by default...
Smells like a perfect situation for some AJAX implementation. I'm not sure caching is the route to go. Caching would probably yield a much faster response after the initial load, but that is still a lot of data to push to the client when the client will only be seeing a small part at any one time. -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
