Combining contracts and exemplar-based programming for class hiding and customization

Lortz, V.B.; Shin, Kang G.

doi:10.1145/191080.191150

Cited by 9 publications

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

Architectural support for quality of service for CORBA objects

Zinky¹,

Bakken²,

Schantz³

1997

Theory Pract. Obj. Syst.

296

View full text Add to dashboard Cite

CORBA is a commercial standard for distributed object computing which shows great promise in the development of distributed programs. Its interface description language (IDL) enables objects to be developed independently of the underlying programming language, operating system, or computer architecture on which they will execute. Programs deployed in a wide-area distributed system encounter conditions which are much more hostile and varying than those operating in a single address space or within a single local area network. In this paper we discuss four major problems we have observed in our developing and deploying wide-area distributed object applications and middleware. First, most programs are developed ignoring the variable wide area conditions. Second, when they do try to handle these conditions, application programmers have great difficulty because they are different from the local objects they are used to dealing with. Third, IDL hides information about the tradeoffs any implementation of an object must make. Fourth, there is presently no way to systematically reuse current technology components which deal with these conditions, so code sharing becomes impractical.In this paper we also describe our architecture, Quality of Service for CORBA Objects (QuO), which we have developed to overcome these limitations and integrate their solution by providing QoS abstractions to CORBA objects. First, it makes these conditions first class entities and integrates knowledge of them over time, space, and source. Second, it reduces their variance by masking. Third, it exposes key design decisions of an object's implementation and how it will be used. Fourth, it supports reuse of various architectural components and automatically generates others.This work is sponsored by Rome Lab.

show abstract

Architectural support for quality of service for CORBA objects

Zinky¹,

Bakken²,

Schantz³

1997

Theory Pract. Obj. Syst.

296

View full text Add to dashboard Cite

show abstract

Aster: a CORBA-based software interconnection system supporting distributed system customization

Issarny

Bidan

Proceedings of International Conference on Configurable Distributed Systems

View full text Add to dashboard Cite

How and why to encapsulate class trees

Riehle

1995

Proceedings of the Tenth Annual Conference on Object-Oriented Programming Systems, Languages, and Applications

View full text Add to dashboard Cite

A good reusable framework, pattern or module interface usually is represented by abstract classes. They form an abstract design and leave the implementation to concrete subclasses. The abstract design is instantiated by naming these subclasses. Unfortunately, this exposes implementation details like class names and class tree structures. The paper gives a rationale and a general metaobject protocol design that encapsulates whole class trees. Clients of an abstract design retrieve classes and create objects based on class semantics specifications. Using abstract classes as the only interface enhances information hiding and makes it easier both to evolve a system and to configure system variants.

show abstract

Combining contracts and exemplar-based programming for class hiding and customization

Cited by 9 publications

References 18 publications

Architectural support for quality of service for CORBA objects

Architectural support for quality of service for CORBA objects

Aster: a CORBA-based software interconnection system supporting distributed system customization

How and why to encapsulate class trees

Contact Info

Product

Resources

About