Atlas: a case study in building a web-based learning environment using aspect-oriented programming
Proceedings of the 14th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Aspect-oriented programming: Introduction
Communications of the ACM
Cascading Style Sheets: The Definitive Guide
Cascading Style Sheets: The Definitive Guide
Implementing Sap Sales and Distribution
Implementing Sap Sales and Distribution
XSLT and XPATH: A Guide to XML Transformations
XSLT and XPATH: A Guide to XML Transformations
The Art of the Metaobject Protocol
The Art of the Metaobject Protocol
A Context-Aware Decision Engine for Content Adaptation
IEEE Pervasive Computing
Supporting Adaptive Multimedia Applications through Open Bindings
CDS '98 Proceedings of the International Conference on Configurable Distributed Systems
Worldwide computing with universal actors: linguistic abstractions for naming, migration, and coordination
A Theory of Distributed Objects
A Theory of Distributed Objects
XML11: an abstract windowing protocol
Science of Computer Programming - Special issue: Principles and practices of programming in Java (PPPJ 2004)
Supporting reconfigurable object distribution for customized web applications
Proceedings of the 2007 ACM symposium on Applied computing
A code migration framework for AJAX applications
DAIS'06 Proceedings of the 6th IFIP WG 6.1 international conference on Distributed Applications and Interoperable Systems
Comparing three coordination models: Reo, ARC, and PBRD
Science of Computer Programming
Ten years of analyzing actors: Rebeca experience
Formal modeling
Decidability problems for actor systems
CONCUR'12 Proceedings of the 23rd international conference on Concurrency Theory
| Hi-index | 0.01 |
In order to guarantee certain levels of QoS, a Web application needs to adapt itself to different execution contexts. However, because of the lack of coordination support in Web platforms, service providers respond to the challenge by simply providing multiple versions of a Web application, one for each context. We argue this top-down approach is neither efficient nor scalable: developing a context-specific application requires considerable effort and expertise while the ever-changing Internet never stops generating interesting contexts which can be exploited for better deployment. As an alternative, we propose a three-layer, bottomup approach to building context-aware Web applications. At the bottom layer, we characterize a context-specific Web application with a particular component distribution plan which provides details for composing individual objects. In the middle layer, recursively defined configurations provide a bridge which relates high-level context features to low-level component distribution properties, where a configuration is a combination of configurations and/or component distribution properties. At the top level, a context management system selects desirable configurations according to the execution contexts.