30
edits
Talk:Session Restore: Difference between revisions
Jump to navigation
Jump to search
m
Comments on some unresolved questions
m (Comments on some unresolved questions) |
|||
| Line 82: | Line 82: | ||
* Don't re-POST forms. Session Saver will do this. I had 5 duplicate bugzilla bugs once before I realized what was happening. Imagine if I was using a poor shopping cart! --[[User:BillMcGonigle|BillMcGonigle]] 10:54, 21 Feb 2006 (PST) | * Don't re-POST forms. Session Saver will do this. I had 5 duplicate bugzilla bugs once before I realized what was happening. Imagine if I was using a poor shopping cart! --[[User:BillMcGonigle|BillMcGonigle]] 10:54, 21 Feb 2006 (PST) | ||
** If you can trust the maxim 'GET for actions without side effects, POST for actions with side effects' you could simply refuse to do POST on session restore. You can't actually trust that a web developer hasn't just decided to use POST for everything because "long URL's are ugly" but maybe it's the right thing to do anyway. --[[User:BillMcGonigle|BillMcGonigle]] 10:54, 21 Feb 2006 (PST) | ** If you can trust the maxim 'GET for actions without side effects, POST for actions with side effects' you could simply refuse to do POST on session restore. You can't actually trust that a web developer hasn't just decided to use POST for everything because "long URL's are ugly" but maybe it's the right thing to do anyway. --[[User:BillMcGonigle|BillMcGonigle]] 10:54, 21 Feb 2006 (PST) | ||
== Unresolved questions == | |||
''Do we ever want to store cached copies of the pages (i.e. for offline access) or do we just store the urls and load them all? Loading from cache would be snappier.'' | |||
* Well, there's multiple strategies: | |||
*# Don't load more than <n> pages at a time, giving the focussed tab 1st priority, allowing the user to work, and then giving priority to tabs the user is working on, as one tab loads, start another so there are always <n> tabs loading until it's recovered. | |||
*#:Advantages - user can work immediately, system is kept under moderate load, restore is probably transparent since any page the user works on is given priority. | |||
*# Load all from cache, then update as visited | |||
*#: Advantages - with luck the cached version should be what the user saw. But if it is we'll only know it if we reload, if it isn't then its misleading, and in any case since we then probably reload pages anyhow does the user benefit from loading the cached version of pages first? | |||
*# Check latest update times of all pages quickly (a lower bandwidth job), and those that have update times matching the cache entry, assume the cache is up to date, otherwise load from web as per (1). | |||
*#: Advantages - many pages will be up to date, so this saves reloading pages other than those changed. In theory this, compbined with 91) for loading web pages that do need reloading, should work. But would it? | |||
: [[User:Foxxen2|Foxxen2]] 09:24, 30 March 2006 (PST) | |||
''Make sure that if the state of the current session crashes the browser, it doesn’t reload at startup and crash over and over again. Look into how SessionSaver and Total Recall detect this.'' | |||
* Whats really helpful would be a FF extension and page processing calls log that can be relied upon to note extension calls made (and their successful return) and page render or page processing calls made (and their successful completion). In theory when it crashes, very few extensions or pages will actually have commenced a call but not completed. Those will likely be the problem ones. beyond that its a problem with FF core code, and a safe start or debug session. The core of the problem is having a way to narrow down problematic pages and extensions. Perhaps if it crashes during a restore it offers to switch to a "safe restore" mode (as opposed to "safe mode"), where extensions are loaded one by one, then pages loaded one by one, and the cause of the crash identified and reported for debugging? Ie a fallback mode for restore where the user gets a slower restore, that keeps as many pages and extensions as it can alive. [[User:Foxxen2|Foxxen2]] 09:24, 30 March 2006 (PST) | |||
''Should form state include saving checkbox and selectbox state as well as text input?'' | |||
* Yes. See above, re text box contents, same applies. [[User:Foxxen2|Foxxen2]] 09:24, 30 March 2006 (PST) | |||