Question on Arrays of data in Tableview

Could someone pleaes help explain a few questions. I have created an api that returns maybe at most

150 - 200 records (just text data in columns, no images or anything like that). With that being said, what would be the best way to display the data.


1 would it be ok to get the records from a call to the API and load all of them into an array, and then load a table.


2. Would it be better to get all the records and load them into an array and then do some type of paging off the array

when scrolling in the table. I think this is the best option, but would an IPhone's memory allow this. Would I need

to keep track of pagenumber pagesize last loaded in the Table.


3. Would it be bettter to add paging to my api and then keep track of pagenum, pagesize in the ios app, and then

keep making calls to the api when scrolling up or down? This would work, but it would mean constant calls to

the api (where the full colleciton would need to be queried each time (for all the data in query) and then only the

correct pagenumber and size be returned. I think this would be higher overhead and slow.



What is the best way to do this?


David.

4. Store data in a plist and use it to populate the table view as needed.


Might help if you talked about the composition of each record, tho.

Regarding the user interface side of things, if you use a UITableView or UICollectionView to display the data, they will "ask" you for the cell for each row or item as it is needed, and basically it only asks for what will be visible on screen. So you don't have to worry about paging, you just implement cellForRowAtIndexPath or cellForItemAtIndexPath, and include code to get the data for the row or item that is passed in a parameter and set the display elements in your cell.

Question on Arrays of data in Tableview
 
 
Q