It is said that the iPhones up to 3G have 128megz, the 3GS has 256mb of RAM in total. That RAM however certainly is shared among applications, OS and the GFX adapter. Overall I would not try to do anything bigger than 64mb and it is said these 64mb also are the biggest amount of RAM that a single application was able to allocate (if available at all).
For what its worth, another limit would be 24mb in total usable for OpenGL textures - just mentioned it cause I had to deal with it myself and thought it would fit the subject of RAM constraints on our beloved device. I do not know if Safari imposes additional memory limitations to web-pages that are displayed on the iPhone. > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Wai Yip > Sent: Tuesday, October 20, 2009 4:23 AM > To: iPhoneWebDev > Subject: Re: How to stop Safari to reload a page? > > > Thank you. This sound like a good idea. And then I have research about > the RAM. 3G only have 128M? Well, I have really try to live within > means. > > On Oct 19, 4:21 am, Niels Leenheer <[email protected]> wrote: > > > My application is mostly implemented in a single web page, with the > > > user build up data over a long stretch of time. The problem is > > > whenever the user move between a different page (tab) in Safari, or > > > when they go to the home screen and then re-enter Safari, the browser > > > is very prone to reload the page. This causes the user to lost of the > > > data he is still constructing. Is there a way to prevent it from > > > automatically reloading the page? > > > > No. You have no control over if and when Safari reloads the page. This is > a > > problem that is directly related to the limited memory that phones > currently > > have compared to desktop systems. > > > > If you leave the page - either by going to a different page or by going > to > > the home screen it will keep the current page in memory. However, if that > > memory is needed for something else it will remove it. If you return to > the > > page and it is still in memory Safari will show the already loaded page. > If > > it isn't in memory any more it will reload the page. > > > > There is a way to solve this though. You could use HTML5 database storage > to > > store the current state of the application. After a change you update the > > database to reflect the new state. If the app is interrupted and needs to > be > > reloaded you could restore the state of the app using the data in the > > database. > > > > I use this method in my own app: MediatankController. It's an app that > lets > > you browse your network media player. Every time the user opens a > directory, > > it is retrieved from the server in JSON format. I store this information > in > > the database. I also store the current location in the directory tree in > the > > database. Using this information I can completely rebuild the last known > > state of the application. The user can just continue with what he was > doing > > before the app was interrupted. > > > > Cheers, > > > > Nielshttp://rakaz.nl > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
