In that case I think your best bet is what Evert suggested: split your XML into multiple smaller, more manageable files. The splitting could take place either on your server that generates the original XML or as a separate process prior to saving theXML to CD. You could probably even incorporate the logic that tells your app which XML "chunk" to retrieve right into the swf, since the search criteria will be known to your application at runtime.
--- In [email protected], "wayneposner" <[EMAIL PROTECTED]> wrote: > > --- In [email protected], "Doug Lowder" <douglowder@> > wrote: > > > > I had some of the same issues reading XML over HTTP. If your XML is > > dynamically generated by a server (via JSP, CF, ASP, etc.), you can > > do what I did, which is to essentially pass your search values as > > parameters within your HTTP request and have the server pass back > > only the data that match those criteria. > > > > Hope that helps, > > Doug > > > > Initially, the XML will be generated by a server, but after that, the > server is completely out of the picture. Unfortunately, the XML will > then be on burnt to CD which may then be copied to some stand-alone > PC. There will be no server involved once the swf is running. Any > other ideas? > > Wayne > -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
