In my opinion, a huge XML tree sent to the client is a design flaw. If it's coming from a 3rd party source, it should be proxied onto a server under your control. From there it should be trimmed down and/or parameterized to send the smallest possible payload to the client.
-Jeff ________________________________ From: Gabe Harbs <harbs.li...@gmail.com> Sent: Friday, February 16, 2018 5:23 AM To: users@flex.apache.org Subject: Re: Lazy parsing inf Flex That’s really interesting. Currently in Royale, we’re using browser methods to parse XML, so the entire tree is parsed into a DOM tree at once. I wonder if that’s something that we can/should optimize… Harbs > On Feb 15, 2018, at 10:40 PM, Alex Harui <aha...@adobe.com.INVALID> wrote: > > It also turns out that Flash lazily parses XML, so when the XML arrived as > a String from the server, Flash only converted the top-level tags into XML > nodes and just remember the strings of tags for SalaryHistory.
