I need to build a list from an xml file that is 700k online or 400k locally (if I edit out the unneccessary data). The list will be hierarchical, not one long list. The user will make some choices from the list the first time the program is run but not after that (usually).
I'm new to BB development (obviously) but not new to Java development. I'm fairly sensitive to the memory limitations imposed by the runtime enviroment (i.e. a handheld device). I'm also sensitive to the slow (compared to broadband) data rate.
Here's my question. Is it better to have the use wait initially for the 700k file to be downloaded and parsed, knowing it's a one-time operation, or is it preferable to include the data with the app? The latter method means the app will be carrying around a large chunk of data that may never be needed again.
After typing this I think I'm leaning toward the former method. However, I'd like to know what experienced developers think. Any inputs are welcomed.
IMO, 700k is a really big download. If the data is static, I'd look to store the data in the app. But, probably not as XML. While good in many respects, XML is very bulky for wireless. We've done projects where converting from XML to CSV gave us a file 1/5th the size.
If possible, a better approach might be to download parts of the data as needed during the init. This is assuming you don't need the entire dataset.
Best way to deal with large data 
