Partitioning web applications between the server and the client

Authors:
Janne Kuuskeri;Tommi Mikkonen
Affiliations:
Department of Software Systems, Tampere University of Technology, Tampere, Finland;Department of Software Systems, Tampere University of Technology, Tampere, Finland
Venue:
Journal of Web Engineering
Year:
2010

Citing 7
Cited 4

A cookbook for using the model-view controller user interface paradigm in Smalltalk-80

Journal of Object-Oriented Programming
A unified platform for data driven web applications with automatic client-server partitioning

Proceedings of the 16th international conference on World Wide Web
Secure web applications via automatic partitioning

Proceedings of twenty-first ACM SIGOPS symposium on Operating systems principles
Practical DWR 2 Projects (Practical Projects)

Practical DWR 2 Projects (Practical Projects)
Restful web services

Restful web services
Web applications: spaghetti code for the 21st century

Web applications: spaghetti code for the 21st century
Web browser as an application platform: the lively Kernel experience

Web browser as an application platform: the lively Kernel experience

Transforming the web into a real application platform: new technologies, emerging trends and missing pieces

Proceedings of the 2011 ACM Symposium on Applied Computing
Extending XForms with server-side functionality

Proceedings of the 27th Annual ACM Symposium on Applied Computing
XFormsDB: an extensible web application framework built upon declarative W3C standards

ACM SIGAPP Applied Computing Review
Performance Evaluation of a Modern Web Architecture

International Journal of Information Technology and Web Engineering

Quantified Score

Hi-index	0.00

Visualization

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 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 address the issues of complexity that have lately emerged in web development.