Practices for preserving expensive view elements


#1

I’m still trying to wrap my head around Ember and am planning to use it with an application that makes heavy use of OpenLayers for interactive mapping.

I’m worried that tying the JS map object and DOM subtree to views will result in performance issues as the user navigates away from that map view and back to it. What options are available to preserve these view elements so they don’t have to be regenerated when the user returns to them? Ember.ContainerView looks appropriate, but I’m not sure it’s what I’d want.