Recently I got in a project which use Tree objects to visualize and manipulate objects. The data source of this object must to be the same but with different visualizations. In some views this tree will be filtered and in other places it won't. The data source must to be kept consistently, if an object is update in a tree, it should reflect the updates in the other Trees.
My question is quite simple, does ArrayCollections are really expensive objects in terms of memory even using the same data source? Or does it have to do with the fact they are manipulating different datasources as well?
Please share your experiences.
ArrayCollection is a very useful construct.
Just make sure you clean the open nodes and it will perform fine.
That is my two cents