I don't understand what you mean. The browser stores the document history whether we want to or not. We have no control over it. The only exception is AJAX, but in a real application there will be many parts where AJAX is turned off for many buttons and links for a variety of reasons (navigation, etc.) This was the case with my app, at least.
The users *will* click on the back button and *will* click on old actions. Currenly, if enough state is still around (which is usually the case), the actions will do the right thing. If the state isn't around (which happens occassionally), the actions will do something semi-reasonable. By semi-reasonable, I mean something that doesn't freak people out too much. Actually, I think I understand now what you mean. The fact that AJAX isn't kept in the history? Then yes, whenever there is AJAX request for a given URI (other than the first AJAX request for that URI), we can safely garbage collect the actions of the the previous request because the page has no chance of being cached in the browser. I was mostly concerned about non-AJAX requests, which are a big part of most applications. Does this clear up what I meant? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" 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/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
