Best solution i see is to use LocalDatabase to store datas. Then for
each call, test if the data is already stored.
R.
Le 27 oct. 10 à 01:24, DaveInATL a écrit :
I am developing an iPhone web app that frequently has to hit my
website via a jQuery AJAX call for data. Let's suppose that the data
consists of statistics for a selected metric for a selected
geographical area. Even when a user reselects the same combination of
metric and area, the web app refetches the data.
I've considered the idea of saving the statistics for a given metric &
area combination, and then producing those statistics from memory
instead of fetching them again.
My concern is that I don't know how much memory is available for this
type of thing in JavaScript on the iPhone. Possibly I can make up a
test that will help me get an idea, but that won't conclusively tell
me the minimum amount of memory that I can count on at all times.
The main reason I would "cache" the data in this way is to improve
performance on an old (slow) iPhone. On a new iPhone, this probably
wouldn't be worth the effort.
Does anyone know how much memory we can use on the iPhone in a web
app?
What happens when you run out of memory?
Any other thoughts?
Thank you.
--
You received this message because you are subscribed to the Google
Groups "iPhoneWebDev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected]
.
For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en
.
--
You received this message because you are subscribed to the Google Groups
"iPhoneWebDev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/iphonewebdev?hl=en.
