Three steps to views: extending the object-oriented paradigm
OOPSLA '89 Conference proceedings on Object-oriented programming systems, languages and applications
Subject-oriented programming: a critique of pure objects
OOPSLA '93 Proceedings of the eighth annual conference on Object-oriented programming systems, languages, and applications
On the semantic diversity of delegation-based programming languages
Proceedings of the tenth annual conference on Object-oriented programming systems, languages, and applications
Subject-oriented composition rules
Proceedings of the tenth annual conference on Object-oriented programming systems, languages, and applications
A flexible operation execution model for shared distributed objects
Proceedings of the 11th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Using role components in implement collaboration-based designs
Proceedings of the 11th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Call graph construction in object-oriented languages
Proceedings of the 12th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Effective distribution of object-oriented applications
Communications of the ACM
Design of class hierarchies based on concept (Galois) lattices
Theory and Practice of Object Systems - Special issue high availability in CORBA
Principles of Database Systems
Principles of Database Systems
Enterprise frameworks: issues and research directions
Software—Practice & Experience - Special issue: Enterprise frameworks
Separation of concerns in hybrid component and agent systems
International Journal of Communication Networks and Distributed Systems
| Hi-index | 0.00 |
There has been a lot of interest recently in the problem of building object-oriented applications by somehow combining other application fragments that provide their own overlapping definitions or expectations of the same domain objects.We propose an approach based on the split objects model of prototype languages whereby an application object is represented by a varying set of instances-- called views-- that implement different parts of its domain behavior but that delegate its core functionalities to a core instance: an object's response to a message depends on the views currently attached to its core instance.Our approach is not purely prototype-based in the sense that core instances and views are members of classes. Further, we recognize that the behavior inherent in views (classes) is often an adaptation of a generic behavior to the domain object at hand, and define viewpoints as parameterized class-like algebraic structures to embody such a generic behavior.In this paper, we first describe view programming from the perspective of the developer. Next, we sketch a semi-formal model of view programming, and describe the steps needed to implement it in a class-based statically typed language, for instance, C++. Third, we look at the challenges and opportunities provided by view programming to support safe, robust, and efficient distributed applications.