Skip to Content

Changes for page ERPrototaculous

Last modified by Ravi Mendis on 2010/11/18 05:07
From version 129.1
edited by Ravi Mendis
on 2010/02/12 18:43
Change comment: There is no comment for this version
To version 128.1
edited by Ravi Mendis
on 2010/02/12 18:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -96,11 +96,10 @@
96 96  One notable difference between the ERPrototaculous and Ajax frameworks is in the way they handle ajax responses.
97 97  In ERPrototaculous, updates and actions break with //The WebObjects Way// by being pseudo-stateless.
98 98  
99 -WebObjects typically vends a fresh response for each and every action. With ajax, this is not necessary.
99 +In a typical WebObjects application, when a user navigates to the previous page using the browser back button and subsequently clicks on a link in on that page, WebObjects needs to remember how to handle that action and to return the correct page. This is no longer necessary for ajax.
100 100  
101 -In a typical WebObjects application, when a user clicks on the back button and clicks on a link in on that page in the browser history, WebObjects needs to remember how to handle that action and to return the correct page. This is no longer true for ajax.
102 -The reason is a user never travels backwards or forwards through the ajax application history.
103 -(i.e there is no forward/back buttons in a 100% ajax app - as there aren't in desktop apps).
101 +A user never travels backwards or forwards through the ajax application history.
102 +(i.e there is no forward/back buttons for ajax requests - just as there aren't forward/back buttons on desktop apps).
104 104  
105 105  So for ajax, the current state of the page fragment component is all that is necessary.
106 106