Skip to Content

Changes for page ERPrototaculous

Last modified by Ravi Mendis on 2010/11/18 05:07
From version 256.1
edited by Ravi Mendis
on 2009/07/16 09:17
Change comment: There is no comment for this version
To version 261.1
edited by Ravi Mendis
on 2009/07/16 09:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,10 +7,10 @@
7 7  Features include:
8 8  
9 9  * 'Organic' support for Prototype and Scriptaculous in WebObjects.
10 +* Use of [[Unobtrusive Javascript>>http://en.wikipedia.org/wiki/Unobtrusive_JavaScript]].
11 +* Pseudo-stateless ajax responses
10 10  * No custom Prototype extensions
11 11  * A set of widgets in the Prototype + Scriptaculous family.
12 -* Use of [[Unobtrusive Javascript>>http://en.wikipedia.org/wiki/Unobtrusive_JavaScript]].
13 -* Virtually stateless ajax responses
14 14  
15 15  ==== Unobtrusive Javascript in ERPrototaculous ====
16 16  
... ... @@ -31,6 +31,8 @@
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 +
34 34  ===== Ajax.Request =====
35 35  
36 36  Prototype's [[Ajax.Request>>http://www.prototypejs.org/api/ajax/request]] is in the form of:
... ... @@ -38,6 +38,8 @@
38 38  * AjaxRequestLink
39 39  * AjaxRequestButton
40 40  
43 +These are used for strictly **background** ajax communication.
44 +
41 41  ==== Prototype + Scriptaculous Widgets ====
42 42  
43 43  * Accordion
... ... @@ -60,3 +60,13 @@
60 60  ** WOSubmitButton (if the result is to update whole page/app.
61 61  ** AjaxUpdaterButton (to update a **container**). Or
62 62  ** AjaxRequestButton (for a background ajax request)
67 +
68 +== Ajax Page Caching 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 instance.
74 +
75 +The reason returning a new context is not necessary is because a client never travels back or forwards through an ajax application unlike in a typical WebObjects app.
76 +Here the current state (or context) of the update or action is all that is necessary.