> 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.
When implementing a similar strategy to save the state of an application with a lot of data, I ran into the 5 second time problem. Although there is plenty of memory, it can take longer than 5 seconds to save or restore the data. Obviously, I can continue by looking at what has been retrieved, but is there an event fired when the timeout occurs by any chance? That would make life easy. Surprisingly, Safari doesn't throw an exception I can catch, the read or write just terminates early with partial data. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
