I don't follow you? Step through a scenario where you think there's a problem.
Btw, this isn't directly related to Continuity, but may tie into your concerns: If I start writing an email in Mail, then switch to another app, then quit Mail from multitasking, the next time I load Mail it has my email waiting. Quitting unexpectedly from the multitasking should be similar to being purged from memory suddenly (i.e. the cause of the reloading that you're seeing). So it shows that it was the act of going into the background where the state of the Mail app was saved to storage to be restored later.
Ok, I'm sorry, I admit that probably is difficult for me to translate my ideas since english is not my first language. I didn't meant that this is related to Continuity, I was thinking that the problem could be worst with Continuity.
Anyway, you are right with this scenario, but the problem I see now is that many apps are not recovering from their status, but they reset and reload without the previous entered queries/data/etc, so I'm curious if this problem can affect the native apps also, and so Continuty (yet in ios 8).
I'll make some examples here with non native apps that doesn't recover from their status correctly when multitasked (it's not always, but very often since ios 7):
- youtube, doesn't remember search/query, or where you are watching a video, it resets to default
- Twitter, reload everything and doesn't remember where you left
- Feedly, same as above, reset where you left reading articles, so you lose the feed etc
- Facebook, ok is rubbish, but as above, reset everything
- Google maps, as above, fast switching in multitasking can reset your query and goes to default
- Gmail, reload everything and restart from login...
There are more I can't remeber now, but basically every app behave like this when multitasked intensively. The only one I can recall now is goodreader, but probably because it writes the status in a sort of temporary file.
Say you need to do some cut & paste between apps and this can be a real annoying problem...
----------
True, although if the content has changed this may be tricky. It makes you wonder what the reasoning for not preserving a cache of the entire page is (rather than just the URL).
I'm guessing one concern is that pages can be quite large and storing multiple tabs would take a chunk of storage and the read/write operations may take a while. Any other ideas?
The problem is that this happens also with one tab, so I don't know if this is about storage. Also, reading from storage isn't faster than reload via cell-data the page (it also preserves internet traffic)? Why not just timing the use, I mean: if the app is not used for 5/10/20/whatever minutes, then it reloads. Otherwise the status is saved.
edit: some typo
