How big xml file we can parse in iPhone application

Question

I will have xml file on server. It will store information of about 600 stores. information includes name, address, opening time, coordinates. So is it ok to parse whole file into iphone then select nearest stores according to coordinates?

I am thinking about processing time and memory use

Please suggest

Answer 1

The way I would do this is write a web service and pass it the coordinates and download only those within a certain radius. Always try to download as little data as possible to the iPhone (especially xml data)

Answer 2

I just put this here http://quatermain.tumblr.com/post/93651539/aqxmlparser-big-memory-win

Answer 3

A simple solution would be to group them into clusters that are somehow related, probably by location. You already have an XML on a server, so simply split them up into 3 groups of related stores of around 200, or preferably even smaller. I'm not entirely sure on why you would want to store 600 data points of that nature. I feel that if you filter/shrink on the server side you could be saving a lot of time/memory.

I have seen people storing 300-400 data points, though it is so dependent on how large your defined objects in your Core Database are, that it is probably best for you to just run some tests.