Skip to Content

Changes for page Development-Backtracking

Last modified by Pascal Robert on 2010/09/13 00:29
From version 10.1
edited by Pascal Robert
on 2010/09/13 00:29
Change comment: There is no comment for this version
To version 9.1
edited by Pascal Robert
on 2010/09/13 00:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,10 +1,10 @@
1 1  == Backtracking ==
2 2  
3 -When Component Actions are used with WebObjects, to be able to preserve state across requests, the server must maintain a cache of previously visited pages. This page cache has a limited size. As a result, if the user presses the back button too many times to the point of exhausting this cache, it will result in a "User has backtracked too far" error.
3 +When Component Actions are used with WebObjects, to be able to preserve state across requests, the server must maintain a cache of previously visited pages. This page cache has a limited size. As a result, if the user presses the back button too many times to the point of exhausting this cache, it will result in a "User has backtracked too far" error.
4 4  
5 5  == Prevention with Direct Actions ==
6 6  
7 -Because direct actions don't require page state like component actions, the best way to avoid backtracking problems is to use [[doc:Development-Direct Actions]] in your app.
7 +Because direct actions don't require page state like component actions, the best way to avoid backtracking problems is to use [[Development-Direct Actions]] in your app.
8 8  
9 9  == Old Sessions and Backtracking ==
10 10  
... ... @@ -25,7 +25,7 @@
25 25  
26 26  This will prevent the session from working if someone uses the back button, but it doesn't prevent them from seeing the content on the pages. If sensitive content is the issue, the best thing to do is to close the window when the user logs out. This would assume that when they loged in, you opened a window for the sensitive part of the app to run in. That way, when you use javascript to close it, you won't trigger a warning message that the user can intercept. With a window that you opened, you can do the redirect like above, to an html page that looks like:
27 27  
28 -{{code 0="xml"}}
28 +{{code value="xml"}}
29 29  
30 30  <HTML>
31 31  <HEAD>