Janne Kuuskeri
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.
- W. W. W. Consortium. Document object model. http://www.w3.org/DOM/, 2004.Google Scholar
- W. W. W. Consortium. Html 5. http://www.w3.org/html/wg/html5/, 2008.Google Scholar
- D. Crockford. Json. RFC 4627, 2006.Google Scholar
- D. Flanagan. JavaScript: The Definitive Guide. O'Reilly Media, Inc., 2006. Google ScholarDigital Library
- N. Ford. Art of Java Web Development: Struts, Tapestry, Commons, Velocity, JUnit, Axis, Cocoon, InternetBeans, WebWork. Manning Publications, 2003. Google ScholarDigital Library
- M. Foundation. The same origin policy. http://www.mozilla.org/projects/security/components/same-origin.html, 2001.Google Scholar
- M. Foundation. Rhino: Javascript for java. http://www.mozilla.org/rhino/, 2008.Google Scholar
- M. Foundation. Spidermonkey (javascript-c) engine. http://www.mozilla.org/js/spidermonkey/, 2008.Google Scholar
- J. J. Garrett. Ajax: A new approach to web application. http://www.adaptivepath.com/ideas/essays/archives/000385.php, 2005.Google Scholar
- Google. Google gears. http://gears.google.com/, 2008.Google Scholar
- A. T. H. III. Ajax: The Definitive Guide. O'Reilly Media, Inc., 2005.Google Scholar
- A. Inc. Jaxer. http://aptana.com/jaxer, 2008.Google Scholar
- G. Krasner and S. Pope. A cookbook for using model-view-controller user interface paradigm in smalltalk-80. Journal of Object-Oriented Programming, 1988. Google ScholarDigital Library
- E. A. Mayer. CSS: The Definitive Guide, Third Edition. O'Reilly Media, Inc., 2006. Google ScholarDigital Library
- T. Mikkonen and A. Taivalsaari. Web applications -- spaghetti code for the 21st century. Technical report, Sun Microsystems, 2007.Google Scholar
- C. Musciano and B. Kennedy. HTML: The Definitive Guide, Third Edition. O'Reilly Media, Inc., 1999. Google ScholarDigital Library
- E. T. Ray. Learning XML, Second Edition. O'Reilly Media, Inc., 2003. Google ScholarDigital Library
- A. Russell. Comet: Low latency data for the browser. http://alex.dojotoolkit.org/?p=545, 2006.Google Scholar
- A. Russell. Comet: Low latency data for the browser. http://alex.dojotoolkit.org/wp-content/LowLatencyData.pdf, 2006.Google Scholar
- A. Russell, G. Wilkins, D. Davis, and M. Nesbitt. Bayeux protocol. Technical report, The Dojo Foundation, 2007.Google Scholar
- A. Taivalsaari, T. Mikkonen, D. Ingalls, and K. Palacz. Web browser as an application platform: The lively kernel experience. Technical report, Sun Microsystems, 2008. Google ScholarDigital Library
- F. Zammetti. Practical DWR 2 Projects. Apress, 2008. Google ScholarDigital Library
- C. Zumbrunn. Helma. http://dev.helma.org/, 2008.Google Scholar
Index Terms
- Partitioning web applications between the server and the client
Recommendations
Client-server web applications widgets
WWW '13 Companion: Proceedings of the 22nd International Conference on World Wide WebThe evolution of the Web from a content platform into an application platform has raised many new issues for developers. One of the most significant is that we are now developing distributed applications, in the specific context of the underlying Web ...
Partitioning web applications between the server and the client
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 ...
Declarative web-applications without server: demonstration of how a fully functional web-application can be built in an hour with only HTML, CSS & Javascript Library
OOPSLA '09: Proceedings of the 24th ACM SIGPLAN conference companion on Object oriented programming systems languages and applicationsCommon wisdom in web-application design states that web-applications need to have (1) a presentation layer (on the browser), (2) a business-logic layer (on the server), and (3) a database. In such a design, almost all of the application behavior is ...
Comments