Note that there are some explanatory texts on larger screens.

plurals
  1. POOptimal way to save/parse XML on iPhone
    primarykey
    data
    text
    <p>This is my first question so I will do my best to conform to the question guidelines. </p> <p>I am developing an iPhone app that parses and XML feed to be displayed in a table. Parsing is not a problem but I am not sure of the best way to optimize loading times after initial run of the app. </p> <p>Here is the different approaches that I am considering:</p> <ol> <li><p>Parse the XML feed each time the application is loaded. <em>Easy way but possibly longer loading time each run of the app.</em></p></li> <li><p>Grab the feed and store it locally (as .xml) then parse locally. Then, each time the app is opened, make an http call to see if the feed has been changed. If not, parse locally. If so, download the new feed and parse locally. <em>The initial loading time will be longer but could be cut down on later runs (if the feed as not been updated). This option will be beneficial if the user has a bad signal but needs to see the data.</em> </p></li> <li><p>Parse the feed and store it into a local sqlite db. Then, each time the app is opened, make an http call the see if the feed has been changed. If so, detect which objects have been added/removed and alter local db accordingly. If not, load data from local db. <em>This might be the best option but I am not sure how long finding the changes will take.</em></p></li> </ol> <p>My feed is only about 100 or so items, each with roughly 20 fields. </p> <p>Initial parsing time:</p> <ul> <li>Roughly 4-5sec with full bars. </li> <li>Roughly 5-7sec with 3 bars.</li> </ul> <p>Any insight as to which option would work best would be very much appreciated.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload