Skip to Content

Changes for page ERPrototaculous

Last modified by Ravi Mendis on 2010/11/18 05:07
From version 236.1
edited by Ravi Mendis
on 2009/07/16 09:46
Change comment: There is no comment for this version
To version 237.1
edited by Ravi Mendis
on 2009/07/16 09:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -31,8 +31,6 @@
31 31  * AjaxUpdaterButton
32 32  * AjaxUpdaterForm (with ##onsubmit## for ajax form submission)
33 33  
34 -These components will update a **container** on the page.
35 -
36 36  ===== Ajax.Request =====
37 37  
38 38  Prototype's [[Ajax.Request>>http://www.prototypejs.org/api/ajax/request]] is in the form of:
... ... @@ -40,8 +40,6 @@
40 40  * AjaxRequestLink
41 41  * AjaxRequestButton
42 42  
43 -These are used for strictly **background** ajax communication.
44 -
45 45  ==== Prototype + Scriptaculous Widgets ====
46 46  
47 47  * Accordion
... ... @@ -64,12 +64,3 @@
64 64  ** WOSubmitButton (if the result is to update whole page/app.
65 65  ** AjaxUpdaterButton (to update a **container**). Or
66 66  ** AjaxRequestButton (for a background ajax request)
67 -
68 -== Page Caching Ajax in ERPrototaculous ==
69 -
70 -One notable difference in the ERPrototaculous and Ajax.framework is in the ajax responses.
71 -ERPrototaculous updates and actions break with "The WebObjects Way" by being pseudo-stateless.
72 -
73 -Instead of returning a new context, an ajax update or action is in fact the same.
74 -
75 -The reason that returning a new context is not necessary is that a client never travels back or forwards through an ajax application unlike in a typical WebObjects app. Here the current state (or context) of the update or action is all that is necessary.