This is a problem that has been addressed numerous times. I suggest
that you search the archives at http://chattyfig.figleaf.com/
pipermail/flashcoders/
The summary is that the speed problem usually has little to do with
the actual xml handling and more to do with how you are updating the
user interface, especially if you are using components. Parse all of
the XML data first, placing the data of interest into an array of
objects. Only once you have built the array should you set your
component's data provider or otherwise update the user interface.
Nathan
http://www.nathanderksen.com
On Jan 31, 2006, at 9:33 AM, Ing. Mario Falomir wrote:
Hi, I need some advice from you guys :) I have an XML Driven FLash
APP,
basically it's a tool that displays charts and data in grids,
containers,
etc...that my client will handout in CDs. So at the beginning of the
development process I thought XML would suit perfectly in the
purpose of
this app. But it happened that the DB used to generate the
apporpiate XML
files that my app consume had grown amazingly so eventually my app
(exclusively the part that searches for an specific registry entry)
turns
very slow and sometimes (rarely but happens) it crashes due to the
exhaustive loops and interations i do in order to the search/
display data of
an specific registry and filtering functions.
So i thouhgt, upon your experience, to ask how would you do to
optimize
this thing or what its the best way to do the queries to an XML in
order
smooth things a little bit more :) Or what approaches (or
guidelines ) do
you use when you have to develop an app. that will have XML to
serve as its
DB. Do you load everysingle XML at once ? on demand ? etc ?
Thanks in advanced!
Mario
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
