| Partitioning web applications between the server and the client |
| Full text |
Pdf
(440 KB)
|
Source
|
Symposium on Applied Computing
archive
Proceedings of the 2009 ACM symposium on Applied Computing
table of contents
Honolulu, Hawaii
SESSION: Web technologies track
table of contents
Pages 647-652
Year of Publication: 2009
ISBN:978-1-60558-166-8
|
|
Authors
|
|
| Sponsor |
|
| Publisher |
|
| Bibliometrics |
Downloads (6 Weeks): 33, Downloads (12 Months): 147, Citation Count: 0
|
|
|
ABSTRACT
Web 2.0 and rich Internet application technologies are offering more and more sophisticated means for building compelling applications. At the same time the development of applications is becoming increasingly complex. While web applications are commonly relying on server-side processing, we aim at implementing a "fat client" and running applications mostly on the client. With this in mind we can derive a set of guidelines on how the applications should be partitioned between the server and the client. By following these directives and leaning on the traditional principles of good software development, we can address the issues of complexity that have lately emerged in web development.
REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
| |
1
|
W. W. W. Consortium. Document object model. http://www.w3.org/DOM/, 2004.
|
| |
2
|
W. W. W. Consortium. Html 5. http://www.w3.org/html/wg/html5/, 2008.
|
| |
3
|
D. Crockford. Json. RFC 4627, 2006.
|
| |
4
|
|
| |
5
|
Neal Ford, Art of Java Web Development: Struts, Tapestry, Commons, Velocity, JUnit, Axis, Cocoon, InternetBeans, WebWork, Manning Publications Co., Greenwich, CT, 2003
|
| |
6
|
M. Foundation. The same origin policy. http://www.mozilla.org/projects/security/components/same-origin.html, 2001.
|
| |
7
|
M. Foundation. Rhino: Javascript for java. http://www.mozilla.org/rhino/, 2008.
|
| |
8
|
M. Foundation. Spidermonkey (javascript-c) engine. http://www.mozilla.org/js/spidermonkey/, 2008.
|
| |
9
|
J. J. Garrett. Ajax: A new approach to web application. http://www.adaptivepath.com/ideas/essays/archives/000385.php, 2005.
|
| |
10
|
Google. Google gears. http://gears.google.com/, 2008.
|
| |
11
|
A. T. H. III. Ajax: The Definitive Guide. O'Reilly Media, Inc., 2005.
|
| |
12
|
A. Inc. Jaxer. http://aptana.com/jaxer, 2008.
|
| |
13
|
|
| |
14
|
|
| |
15
|
T. Mikkonen and A. Taivalsaari. Web applications -- spaghetti code for the 21st century. Technical report, Sun Microsystems, 2007.
|
| |
16
|
|
| |
17
|
|
| |
18
|
A. Russell. Comet: Low latency data for the browser. http://alex.dojotoolkit.org/?p=545, 2006.
|
| |
19
|
A. Russell. Comet: Low latency data for the browser. http://alex.dojotoolkit.org/wp-content/LowLatencyData.pdf, 2006.
|
| |
20
|
A. Russell, G. Wilkins, D. Davis, and M. Nesbitt. Bayeux protocol. Technical report, The Dojo Foundation, 2007.
|
| |
21
|
A. Taivalsaari, T. Mikkonen, D. Ingalls, and K. Palacz. Web browser as an application platform: The lively kernel experience. Technical report, Sun Microsystems, 2008.
|
| |
22
|
|
| |
23
|
C. Zumbrunn. Helma. http://dev.helma.org/, 2008.
|
|