Paepcke, A. "PCLOS: stress testing CLOS" ECOOP/OOPSLA'90 Proceedings  Home/Search   Document Not in Database   Summary   Related Articles   Check

....used in applications developed in terms of cooperative information systems are interwoven objects. with monolithic modules of executable code) and then combine these into a final meaningful implementation. Such ideas can benefit tremendously from techniques found in metaobject protocols [KdRB91, Pae90] and reflection [Mae87, HY88] There, a system provides two interfaces to achieve separation and coordination of control: a primary interface that provides the basic functionality, and another that can be used to monitor, reason about and tune the functionality available through the primary ....

A. Paepcke. "PCLOS: Stress testing CLOS". In Proceedings of OOPSLA'90 (Conference on Object-oriented Programming Systems, Languages and Applications), 1990.

....transaction and commit, and object update uses exclusive write locks. The cached object is invalidated by a database alerter, when changed by another application. Per class methods are stored in binary form, and class hierarchy information is stored in OBJFADS system catalogs. 2. 2 PCLOS PCLOS[21, 22] utilizes a virtual database interface, and implements persistence via the CLOS Meta Object Protocol[15] MOP) Protocol adapters map requests from the virtual, relational interface to any of the three specific databases currently supported. A pclos class metaclass is used to include the extra ....

Andreas Paepcke. PCLOS: stress testing CLOS. ACM SIGPLAN Notices, 25(10):221--237, October 1990.

.... Knowledge into Metaobjects David Edmond, Mike Papazoglou, Nick Russell and Zahir Tari School of Information Systems, Queensland University of Technology GPO Box 2434 Brisbane Queensland 4001 Australia email: fdavee,mikep,nickr,zahirtg icis.qut.edu.au Abstract The use of reflection [ Mae87, HY88, Pae90 ] is particularly applicable to multi database systems and to cooperating systems in general. We view such systems as (1) being distributed over a common communication network, and (2) working towards some common goal. Cooperation is achieved by coordinating and exchanging information and ....

Paepcke A. (1990). "PCLOS: Stress Testing CLOS", OOPSLA'90.

....meta object classes constitute the core facilities of its meta object protocol (MOP) The MOP can be used to describe operations and interactions among instances of its meta object classes in a way that allow extensions or modifications of the CLOS implementation. For example, the PCLOS system [Pae90] has added database persistence to CLOS objects by subtyping meta object classes and selectively shadowing methods that operate on their instances. These implementation changes come into effect without requiring any modifications to the existing system code of CLOS. We view cooperating systems as ....

Paepcke A. (1990). "PCLOS: Stress Testing CLOS", OOPSLA'90.

....class ; ii) that it include all of the class s superclasses ; and (iii) that these superclasses include the classes standard object and t. Thus the user may adjust the inheritance behavior over a wide range and yet guarantee other aspects of inheritance. Another example is the PCLOS system [23] which added database persistence to CLOS objects by subtyping meta object classes and selectively shadowing methods that operate on their instances. These implementation changes come into effect without requiring any modifications to the existing system code of CLOS . 2.4. Summary In this ....

Paepcke A. (1990). "PCLOS: Stress Testing CLOS", OOPSLA'90.

....the conventional situation where object materialisation and object instantiation constitute the same process. Until some class constructor is called, the object and the values associated with its state are nowhere. Our approach to bottom up object componentry is carried out by means of reflection [Mae87, HY88, Pae90] which we feel is particularly applicable to client server database applications, and to multidatabase systems in general. We call this operational reflection whereby we construct metaobjects that contain operational knowledge, such as knowledge of location and processing activities. In a ....

Paepcke A. (1990). "PCLOS: Stress Testing CLOS", OOPSLA'90.

....other side changes correspondingly. c) Systems Meta Object Protocols The CLOS meta object protocol [Kiczales,Rivi res,Bobrow 91] is the most prominent example of an open implementation for an object oriented language. Among others, this meta object protocol has been used to make CLOS persistent [Paepcke 90]. Agora [SteyaertEtAl 93] Steyaert 94] CodenieEtAl 94] Steyaert,DeMeuter 95] is a reflective, prototype based language that features a general mixin based approach to (multiple) inheritance. Agora uses its meta object protocol to explore different object oriented programming paradigms within ....

Paepcke, A. "PCLOS: stress testing CLOS"; ECOOP/OOPSLA'90 Proceedings, ACM Press 1990.

....we need to be able to work with abstractions that express, naturally and directly, different system aspects. Then we can combine these into a final implementation. Such ideas can benefit tremendously from techniques found in reflection (Maes 1988) and metaobject protocols (Kiczales et al. 1991, Paepcke 1990), in particular. A metaobject protocol (MOP) is a supplemental interface to a conventional object model. It provides users with the ability to incrementally modify and evolve the behaviour and implementations of objects, in a way akin to changing a programming language s underlying object model. ....

Paepcke, A. (1990), "PCLOS: Stress testing CLOS", in `Proceedings of OOPSLA'90 (Conference on Object-oriented Programming Systems, Languages and Applications)'.

No context found.

Paepcke, A. "PCLOS: stress testing CLOS" ECOOP/OOPSLA'90 Proceedings

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC