Automatic client-server partitioning of data-driven web applications

Current application development tools provide completely different programming models for the application server (e.g., Java and J2EE) and the client web browser (e.g., JavaScript and HTML). Consequently, the application developer is forced to partition the application code between the server and client at the time of writing the application. However, the partitioning of the code between the client and server may have to be changed during the evolution of the application for performance reasons (it may be better to push more functionality to the client), for correctness reasons (data that conflicts with multiple clients cannot always be pushed to clients), and for supporting clients with different computing power (browsers on desktops vs. PDAs). Since the client and server use different programming models, moving application code from client to server (and vice versa) reduces programmer productivity and also has the potential to introduce concurrency bugs. In this demonstration, we ad...

• Type: Conference
• Year: 2006
• Where: SIGMOD
• Authors: Nicholas Gerner, Fan Yang 0002, Alan J. Demers, Johannes Gehrke, Mirek Riedewald, Jayavel Shanmugasundaram
• Keywords: Application Code, Application Server, Database, Partition Hilda Code, SIGMOD 2006