scispace - formally typeset
Journal ArticleDOI

Architectural support for quality of service for CORBA objects

J. Zinky, +2 more
- 01 Jan 1997 - 
- Vol. 3, Iss: 1, pp 55-73
Reads0
Chats0
TLDR
The architecture, Quality of Service for CORBA Objects (QuO), is described, which is developed to overcome limitations and integrate their solution by providing QoS abstractions to CORBA objects.
Abstract
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. While this is sufficient in many environments, 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 application programmers do try to handle these conditions, they have great difficulty because these harsh conditions are different from those of 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. © 1997 John Wiley & Sons, Inc.

read more

Citations
More filters
Proceedings ArticleDOI

An Adaptive Fault-Tolerant Component Model

TL;DR: A component model for building distributed applications with fault-tolerance requirements that selects the configuration of replicated services during execution time based on QoS requirements specified by the user is presented.
Proceedings ArticleDOI

Proteus: a flexible infrastructure to implement adaptive fault tolerance in AQuA

TL;DR: The infrastructure of Proteus, the part of AQuA that dynamically manages replicated distributed objects to make them dependable, is described, along with its use in implementing active replication and a simple dependability policy.

Smart Grid Communications: QoS Stovepipes or QoS Interoperability? 1,2

TL;DR: It is argued that middleware is a key enabling technology for helping meet interoperability requirements and avoid stovepipe systems in the smart grid, and middleware-level mechanisms are a much better way to provide end-to-end QoS and security.
Proceedings ArticleDOI

A quality model for multichannel adaptive information

TL;DR: The model enables a clear separation of modeling aspects of services, networks, and devices and embeds rules enabling the evaluation of end-to-end quality, which can be used to select services according to the actual quality perceived by users.
Journal ArticleDOI

Evaluating meta-programming mechanisms for ORB middleware

TL;DR: This article examines and compares common meta-programming mechanisms supported by DOC middleware and provides a systematic evaluation of these mechanisms to help researchers and developers determine which are best suited to their application needs.
References
More filters
Journal ArticleDOI

RSVP: a new resource ReSerVation Protocol

TL;DR: The resource reservation protocol (RSVP) as discussed by the authors is a receiver-oriented simplex protocol that provides receiver-initiated reservations to accommodate heterogeneity among receivers as well as dynamic membership changes.
Book

The art of metaobject protocol

TL;DR: A new approach to programming language design is presented, which resolves fundamental tensions between elegance and efficiency, and a metaobject protocol is presented that gives users the ability to incrementally modify the language's behavior and implementation.
Book

The Art of the Metaobject Protocol

TL;DR: In this article, the authors present a new approach to programming language design, which resolves fundamental tensions between elegance and efficiency, called metaobject protocols, which are interfaces to the lanaguage that give users the ability to incrementally modify the language's behavior and implementation, as well as to write programs within the language.
Journal ArticleDOI

RSVP: a new resource reservation protocol

TL;DR: A resource reservation protocol (RSVP), a flexible and scalable receiver-oriented simplex protocol, that provides receiver-initiated reservations to accommodate heterogeneity among receivers as well as dynamic membership changes and supports a dynamic and robust multipoint-to-multipoint communication model.
Book ChapterDOI

A Note on Distributed Computing

TL;DR: In this paper, the authors look at a number of distributed systems that have attempted to paper over the distinction between local and remote objects, and show that such systems fail to support basic requirements of robustness and reliability.
Related Papers (5)