Jeff I hope we see some responses to this. I like the idea of non-bindable and immutable DTOs, but isn't it true that if you have a very large list, you've got substantial memory overhead in the conversion of those DTOs to the bindable objects. Or are people tackling that with virtualized collections?
On Mon, Oct 26, 2009 at 12:10 PM, Battershall, Jeff < [email protected]> wrote: > > > I happened across the slides from a presentation that Sean Chirstmann did > at Max 2008 about memory optimization in AIR ( > http://www.craftymind.com/wp-content/uploads/2008/11/sean_christmann_optimizing_air_final.pdf > ). > > > > One of his points was NOT to make DTOs or AMF objects bindable. I’ve been > making my AMF model objects bindable for a long time and I just wanted to > get second opinions from the list. > > > > I can see the point – if model objects are bindable and are bound using > strong references to display object properties using {}, it could result in > object instances persisting when they should be available to the GC. If > true, I have to do significant re-factoring. > > > > I’m looking for corroboration here – anyone care to share their thoughts on > this? > > > > Jeff Battershall > > Application Architect > > Dow Jones Indexes > > [email protected] > > (609) 520-5637 (p) > > (484) 477-9900 (c) > > > >
