I don't think you want to load 25MB of data into Flash Player... bad
things will probably happen. Putting that much into tree a would
almost certainly be a very bad scene. Can you put the data into a
database somewhere and query that?

Ben



--- In [email protected], Gooee Guy <[EMAIL PROTECTED]> wrote:
>
> Thanks for the hint. Yes, I can actually read the file and display
it in a tree control, for example.
> 
> The format of the XML is something like this (simplified):
> 
> <ac val="435">
>    <ph val="2010011">
>    <ph val="2010012">
>    <ph val="2010013">
>    <ph val="2010014">
> </ac>
> <ac val="801">
> 
>    <ph val="2011011">
> 
>    <ph val="2012012">
> 
>    <ph val="2013013">
> 
>    <ph val="2014014">
> 
> 
> </ac>
> 
> Currently, my biggest problem is this: If I just read in the XML
into Flex 3 with an mx:XML tag, everything works fine. I can even
search for specific values and highlight the search result in the tree.
> 
> However, that's for the simplified test scenario. The actual XML
file is about 25MB, and I have to download it weekly (from the
National Do Not Call Registry). So, I thought I had to do something
more elegantly (with HTTPService and XMLList and/or XMLListCollection)
to read in that large XML file.
> 
> And, again, I can read in and display the contents of the XML file,
but I just can't search through the contents of the tree control
anymore when I switch from a simple <mx:XML> tag to either the XMLList
and/or XMLListCollection.
> 
> Any hints? Links? Dope slaps?
> 
> 
> Subject: [flexcoders] Re: Reading & Parsing Large XML File . . .
> 
>                 Do you know the name of the node it would be in? If
so, something like
> this should be all you need:
> 
> uberXml..(phoneNode == "555-555-5555" )
> 
> HTH,
> Ben
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>      
____________________________________________________________________________________
> Be a better friend, newshound, and 
> know-it-all with Yahoo! Mobile.  Try it now. 
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
>


Reply via email to