On Feb 20, 2008 10:43 AM, Tracy Spratt <[EMAIL PROTECTED]> wrote: > Performance caveat: It has become clear that accessing data an xml > node is significantly slower than accessing data in a strongly typed > object. This can be noticable if you have, say, a large datagrid > that displays hundreds of cells. > > If this is the case with your app, then best practice is to pre- > process the e4x xml into strongly typed objects in an ArrayCollection.
Tracy. I'm curious if you think this is applicable for charts as well. We have some charts where we're pulling in hundreds or thousands of data points as XML via HTTPService and the rendering is occasionally slow. I've been ascribing that to the rendering overhead (and have been working to address that -- eliminating drop shadow filter, etc...) but wonder if some of it is just accessing XML data. Thanks, Chris Hunter
