Skip to Content
Last modified by Pascal Robert on 2010/09/13 00:29
From version 8.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
Parent
... ... @@ -1,0 +1,1 @@
1 +How-tos
Content
... ... @@ -10,4 +10,4 @@
10 10  
11 11  Note that the Component Action Request Model has some disadvantages. Each URL, to be handled, must find the matching component object in memory. Thus, once the session has timed out, the URL becomes largely incomprehensible and good handling of this situation is difficult. One option is to add additional values as a query string on the URL - this will not break standard request processing but could be used to provide the correct information to recover if the session is gone. Additionally, sessions cannot remember infinite component objects, unless you want to throw memory at the problem, so by default only 30 are stored. This means it is possible for users to backtrack too far and create problems, especially if you are using multiple frames or windows.
12 12  
13 -For cases where highly interactive pages are not required, you may prefer [[Direct Actions>>Development-Direct Actions]], which has none of these disadvantages, but provides less help.
13 +For cases where highly interactive pages are not required, you may prefer [[Direct Actions>>doc:Development-Direct Actions]], which has none of these disadvantages, but provides less help.