Smalltalk-80: the language and its implementation
Smalltalk-80: the language and its implementation
Concepts and experiments in computational reflection
OOPSLA '87 Conference proceedings on Object-oriented programming systems, languages and applications
OOPSLA '89 Conference proceedings on Object-oriented programming systems, languages and applications
Computational reflection in class based object-oriented languages
OOPSLA '89 Conference proceedings on Object-oriented programming systems, languages and applications
CLOS in context: the shape of the design space
Object-oriented programming
Persistence software: bridging object-oriented programming and relational databases
SIGMOD '93 Proceedings of the 1993 ACM SIGMOD international conference on Management of data
Lisp and Symbolic Computation
Metaclasses and Their Application: Data Model Tailoring and Database Integration
Metaclasses and Their Application: Data Model Tailoring and Database Integration
The Art of the Metaobject Protocol
The Art of the Metaobject Protocol
PCLOS: A Flexible Implementation of CLOS Persistence
ECOOP '88 Proceedings of the European Conference on Object-Oriented Programming
Multi-Data Models Translations in Interoperable Information Systems
CAiSE ;96 Proceedings of the 8th International Conference on Advances Information System Engineering
TOOLS '98 Proceedings of the Technology of Object-Oriented Languages and Systems
Tigukat: a uniform behavioral objectbase management system
Tigukat: a uniform behavioral objectbase management system
Hi-index | 0.00 |
This paper presents an architecture where persistence is added to an object-oriented reflective model in a client-server environment. When the client and the server database management system do not share a common formalism, conversion rules must be set. If the open reflective client has intercession properties and the server does not, for example, when an open reflective language is bound to a relational database management system, we show that the conversion rules may become inadequate when a designer extends the semantics of the client language. An object-oriented reflective system is reified as a metaobject model and intercession is often designed as a metaobject protocol that can be specialized. In this case, we state that the best architecture to bring persistence to a reflective client is to extend the standard metaobject protocol with a fine-grained persistence and conversion protocol. We present such a protocol, and we illustrate it with a binding between Power Classes, an open reflective language, and ObjectDriver, our wrapper to relational databases.